search for: rcppredis

Dear Davis, Thank you a lot for sharing this, and I am happy that I was not the only one who need to do it once to learn:) I proposed to add my repo to the manual. I think it makes sense to add both of ours, if possible, or we could merge them together and add that to the manual. Long-term URL stability is apparently an issue, but I think we may find a solution there. Anyway, thanks a lot for

...unctions to be called_ (which in both cases are from base R as R Core is > very careful not get tied into exporting APIs, which is both understandable > and a source of added difficulty for us package writers) > > RApiDatetime > RApiSerialize > > The latter one is use by my RcppRedis package, Travers' very nice qs > package > and Tim's rpg package. > > To my reading, the R Community is drifting more and more towards collective > amnesia where prior work is (pick any one the following) > > - ignored altogether > - reinvented by another package &...

...y <ripley at stats.ox.ac.uk> wrote: > > This concerns CRAN packages > > Amelia C50 Cubist Cyclops DetSel GENLIB IRISSeismic KSgeneral > MigClim MonetDBLite Numero OpenMx PBSmapping PSPManalysis > PropClust RArcInfo RandomFields RandomFieldsUtils RcppMsgPack > RcppParallel RcppRedis RecordLinkage Rmalschains RnavGraph Rvcg > RxODE SiMRiv antiword bigrquery bsamGP catnet coxme dbarts > dggridR divest dpglasso earth epanet2toolkit fs gap geojsonsf > gglasso graphql hashmap haven hier.part imager iptools jiebaR > kernlab lpridge lvec mlvocab mongolite nandb ore phreeq...

...e very purpose of exporting API functions to be called_ (which in both cases are from base R as R Core is very careful not get tied into exporting APIs, which is both understandable and a source of added difficulty for us package writers) RApiDatetime RApiSerialize The latter one is use by my RcppRedis package, Travers' very nice qs package and Tim's rpg package. To my reading, the R Community is drifting more and more towards collective amnesia where prior work is (pick any one the following) - ignored altogether - reinvented by another package - shadowed by another package rather...

I just (apparently) figured out how to do the stuff described in Section 5.4.2 of Writing R Extensions. I put my test toy packages on github <https://github.com/cjgeyer/linkingTo> for anyone to copy. If anyone cares to read the README and the bits of code it links to and tell me anywhere I am wrong, I would be grateful. But the main point of this e-mail is a complaint about that section

On 29/12/2016 15:55, Simon Urbanek wrote: > The problem is elsewhere - Rinterface.h guards the ultima-ratio fallback with HAVE_UINTPTR_T but that config flag is not exported in Rconfig.h. Should be now fixed in R-devel - please check if that works for you. Rconfig.h would be appropriate if Rinterface.h is being included from C code using the same compiler as used for R. But as Rinterface.h