search for: rf_

...ts from package C code. AFAICT, this isn't allowed since both NewEnvironment and R_NewHashedEnv are declared in Defn.R. If exposing this isn't controvertial, I would submit a patch. However, I'm not sure where the declarations should go (Rdefines.h?) and whether they need to change to Rf_*. + seth

Hi all, I've noticed some peculiarities in the tools:::funAPI output that complicate its programmatic use a bit. - Is it for remapped symbol names (with Rf_ or the Fortran underscore), or for unmapped names (without Rf_ or the underscore)? I see that the functions marked in WRE are almost all (except Rf_installChar and Rf_installTrChar) unmapped. This makes a lot of sense because some of those interfaces (e.g. CONS(), CHAR(), NOT_SHARED()) are C pr...

I am attempting to bring R-3.0.2 functionality into a project with a very large C++ codebase. The existing codebase already has a LENGTH function defined. R also defines a LENGTH function. I first compiled R as a shared library and linked it into this existing codebase, along with RInside. When I run a parseEvalQ with a linear model command it will stack dump. Looking at the backtrace, what is

...mensions On Mon, Jul 15, 2024 at 10:32?AM Ivan Krylov via R-devel <r-devel at r-project.org> wrote: > > Hi all, > > I've noticed some peculiarities in the tools:::funAPI output that > complicate its programmatic use a bit. > > - Is it for remapped symbol names (with Rf_ or the Fortran > underscore), or for unmapped names (without Rf_ or the underscore)? > > I see that the functions marked in WRE are almost all (except > Rf_installChar and Rf_installTrChar) unmapped. This makes a lot of > sense because some of those interfaces (e.g. CONS(), CHAR()...

...> But, there are two functions, log1pexp() and rnbeta(), > which appear in the header file, and not in > ?libRmath.dylib?. > There is a comment in the header, '// <-- > ../nmath/plogis.c? next to log1pexp(). That file, > ?plogis.c? contains a function ?Rf_log1pexp?, which is how > the function would be named without '#define > MATHLIB_STANDALONE?. > The other function, 'rnbeta()? doesn?t appear in any of > the source files in the ?nmath? folder. Maybe a file is > missing. Incidentally (not being an Apple c...

...come up with I would probably be fine as long as it's not alphabetical. While listing everything together in alphabetical order is tolerable, it is easy to get lost when you don't know what you are looking for exactly. Also many functions that serve different purpose all start with (R_* or Rf_*) making alphabetical order more useless. It would also be nice to have a third column with the declarations, but it would be lower priority for me as by now I'm used to grepping whatever declaration I need from the headers. I am not familiar with texinfo, so I don't know if this is a tri...

I am trying to add #include <R.h> to a .c file in one of my package, so I can call error() without a complaint about implicit defined function. The src/ has a Makefile, to build some exec/ files that are needed. Without the include, my Makefile target OBJS = $(SRC:.c=.o) $(PKGNAME).so: $(OBJS) rpcx.h $(R_HOME)/bin/R CMD SHLIB $(OBJS) seems to work fine, and I do not need a target

Dear all, when working on a project with embedded R, I found out that R-2.0.0 causes a problem where older versions worked OK. Rf_findVar(...) causes the following error when used to find a generic function (such as print): fun = Rf_findVar(...); R_tryEval(fun, ...); Error in function (object, ...) : Invalid generic function in usemethod Alternatively, using Rf_findFun(...) seems OK in this context, but crashes if you call...

Hi All, I am new to this area and use Rcpp to call C++ from R and try to build the package under Windows 7. I use Rtools and R 2.10.1 32bit. Everything works fine with me, except using R functions like "rnorm" or "runif" in the C++ code. When I use "R CMD check" the package, it always return error ** libs making DLL ... g++

...r error messages to REprintf(). ===== New namespace "R::" for Rmath functions ===== A side-effect of Rcpp sugar providing vectorised d/p/q/r functions for the various statistical distribution was that the scalar variants of these functions (available from Rmath.h) were masked behind a Rf_ prefix. Previously, one had to call ::Rf_pnorm5() to compute pnorm() -- but now a cleaner interface R::pnorm() is available. Unit tests were added as well. ===== Links ===== Rcpp main page: http://dirk.eddelbuettel.com/code/rcpp.html R-forge project page: http://r-forge.r-project.or...

...r error messages to REprintf(). ===== New namespace "R::" for Rmath functions ===== A side-effect of Rcpp sugar providing vectorised d/p/q/r functions for the various statistical distribution was that the scalar variants of these functions (available from Rmath.h) were masked behind a Rf_ prefix. Previously, one had to call ::Rf_pnorm5() to compute pnorm() -- but now a cleaner interface R::pnorm() is available. Unit tests were added as well. ===== Links ===== Rcpp main page: http://dirk.eddelbuettel.com/code/rcpp.html R-forge project page: http://r-forge.r-project.or...

...xel> PixelPrQueue; SEXP lib_filterInvWS (SEXP x) { SEXP res; int i, j, index; double val; PixelPrQueue pq; int nx = INTEGER ( GET_DIM(x) )[0]; int ny = INTEGER ( GET_DIM(x) )[1]; int nz = INTEGER ( GET_DIM(x) )[2]; int nprotect = 0; PROTECT ( res = Rf_duplicate(x) ); nprotect++; // Pixel px; for (int im = 0; im < nz; im++ ) { double * src = &( REAL(x)[ im * nx * ny ] ); double * tgt = &( REAL(res)[ im * nx * ny ] ); for ( j = 0; j < ny; j++ ) for ( i = 0; i < nx; i++ ) {...

Package: logcheck-database,sendmail-base Version: logcheck-database/1.2.69 Version: sendmail-base/8.14.3-9 Severity: serious User: treinen at debian.org Usertags: edos-file-overwrite Date: 2009-08-18 Architecture: amd64 Distribution: sid Hi, automatic installation tests of packages that share a file and at the same time do not conflict by their package dependency relationships has detected the

...code is the main point where you can hear about interfacing R and Delphi. Other files that may be of interest are: BugsAndQuestions.txt and History.txt --- TRANSLATION CONVENTIONS --- Motto: As close as possible to the syntax/naming of the original headers Changes: - most prefixes ("Rf_", "R_", "do_", ...) and suffixes ("_t") are gone. An exception is "S_" which is shortened to "S" - the underscores ("_") are gone too. CamelCaseStyleConvention is used. - different versions (Rf_asChar, asChar) become one (riAs...

...returned to the caller. o C entry points R_qsort and R_qsort_I now have start and end as size_t to allow them to work with longer vectors on 64-bit platforms. Code using them should be recompiled. o A few recently added C entry points were missing the remapping to Rf_, notably [dpq]nbinom_mu. o Some of the interface pointers formerly available only to R.app are now available to front-ends on all Unix-alikes: one has been added for the interface to View(). o PACKAGE = "" is now an error in .C() etc calls: it was always contra...

...returned to the caller. o C entry points R_qsort and R_qsort_I now have start and end as size_t to allow them to work with longer vectors on 64-bit platforms. Code using them should be recompiled. o A few recently added C entry points were missing the remapping to Rf_, notably [dpq]nbinom_mu. o Some of the interface pointers formerly available only to R.app are now available to front-ends on all Unix-alikes: one has been added for the interface to View(). o PACKAGE = "" is now an error in .C() etc calls: it was always contra...