search for: use_rinternals

Dear Prof Ripley, Prof Brian Ripley wrote: > But it is not taken 'verbatim from src/main/print.c' (at least not in > that version of R), and the code is not run with USE_RINTERNALS defined > when write-barrier checking is enabled. > > The example has been updated to match the current code in 2.7.0 alpha. I just assumed that it is copied verbatim without checking because it says so in the sentence above the code ("As a more comprehensive example of construct...

But it is not taken 'verbatim from src/main/print.c' (at least not in that version of R), and the code is not run with USE_RINTERNALS defined when write-barrier checking is enabled. The example has been updated to match the current code in 2.7.0 alpha. On Sun, 30 Mar 2008, sanders at fs.tum.de wrote: > Full_Name: Simon Anders > Version: 2.6.2 > OS: Ubuntu Linux > Submission from: (NULL) (86.22.75.91) > > &g...

Hi, Somehow function-like macros from Rinternals.h are not defined when I include the file. foo.c ################## #include <R.h> #include <Rinternals.h> #ifndef NILSXP #error("NILSXP") #endif #ifndef INTEGER #error("INTEGER") #endif ################### When compiled: vor/src% gcc -I/usr/local/lib/R/include -g -O2 -c foo.c -o foo.o foo.c:11:2: #error

Hi all, it seems that from R 4.0.1 EXTPTR_PTR can be either a macro or a function, depending on whether USE_RINTERNALS is requested. Jeroen helped me find that this was in 78592: https://github.com/wch/r-source/commit/c634fec5214e73747b44d7c0e6f047fefe44667d This is a problem, because binary packages that are built on R 4.0.1 or R 4.0.2 will potentially not load on R 4.0.0, if they use the EXTPTR_PTR function. E...

...ower pc. Am I would of luck with this package? Stephen Sefick * Installing *source* package ?ifultools? ... ** libs gcc -std=gnu99 -I/usr/local/lib/R/include -I"../inst/include/" -D"MUTIL_STATIC" -D"DEF_TF" -D"INTERRUPT_ENABLE" -D"NDEBUG" -D"USE_RINTERNALS" -I/usr/local/include -fpic -g -O2 -c RS_fra_dim.c -o RS_fra_dim.o In file included from /usr/include/endian.h:37, from /usr/include/sys/types.h:217, from /usr/include/stdlib.h:320, from /usr/local/lib/R/include/R.h:28, fr...

...code, which I wrote following this example, did not compile, complaining about 'CAR(t)' being illegal as l-value. After a while I figured out the reason, which is (as you probably have spotted immediatly) that the example is taken from a code snipped that imports Rinternals.h with defined USE_RINTERNALS, while I followed the manual's advice to not define USE_RINTERNALS for extensions. Maybe you could add a note in this section of the manual that one should use SETCAR and SETCDR instead. A more illustrative example would be even better. Just in case you want to use it as example, here is my...

...extern "C" { #endif and #ifdef __cplusplus } #endif around the function prototypes in Rinternals.h (in /usr/local/lib/R/include on my Red Hat 7.2 box) so my dynamic linker would no longer complain about mangling-related undefined symbols. Also, I had to use #define USE_RINTERNALS before including them in order to get a few macros I suppose are natural to use. To be honest, I do think the include files could do with a bit of cleaning up, in particular in view of linking in C++ code, but no complaints (I'm very happy to have R as it is). My question is this: Our library...

...H) --- The file "Rinternals.h" contains two sets of functions: one with "real" functions who are exported in the R.dll and one with functions that use the structs (records) directly to access the data. The second is intended for use within R itself and is protected by the "USE_RINTERNALS" define. While both "sets" have been translated, only rhRInternals.pas is distributed for now. This may change upon need/request. --- LICENSE --- The Delphi port of the R header files will be published under a dual license (GPL v2.1 / proprietary) later. (End of 2006 at the latest...

...ther we want to generalize this, it would be easy to have this support the full space of metadata for wrappers and be a general purpose wrapper-maker, but that isn't what it is right now. At the C-level, it looks like we do make R_tryWrap available (it appears in Rinternals.h, and not within a USE_RINTERNALS section),so you can call that from your own C(++) code. This creates a wrapper that has no metadata on it (or rather it has metadata but the metadata indicates that no special info is known about the vector). > > > I was trying to create a factor that used an ALTREP integer, but > &gt...

Hello, I?m experimenting with ALTREP and was wondering if there is a preferred way to create an ALTREP wrapper vector without using .Internal(wrap_meta(?)), which R CMD check doesn?t like since it uses an .Internal() function. I was trying to create a factor that used an ALTREP integer, but attempting to set the class and levels attributes always ended up duplicating and materializing the