search for: rcppxts

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

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

...add a section on 'prior art' and references. The canonical > example > always was (c.f. Writing R Extensions) > > lme4 <-> Matrix > > which was followed early by the CRAN packages > > zoo <-> xts > > upon which I built > > xts <-> RcppXts > > with a write-up (from 2013 !!) here: > https://gallery.rcpp.org/articles/accessing-xts-api/ > > Via private mail, I helped then-maintainer Vincent connect expm: > > expm <-> Matrix > > and built two packages on CRAN _for the very purpose of exporting API >...

...age A. Package A uses Rcpp, and I want to extend a class X used there. It doesn't really matter (for the issue at hand) if you use Rcpp or not -- R only offers us C interfaces so C interfaces are all we got. And they don't know classes. I worked through that in some of my packages. See eg RcppXts which "extends" in your sense xts by allowing C++ level access from another package. The one key aspect is that _everything you want to call from B must be explicitly exported by A_. See Writing R Extensions for details. If you could rewrite your class A to be header-only then you could...

Jitao, Thanks for writing this up. You could add a section on 'prior art' and references. The canonical example always was (c.f. Writing R Extensions) lme4 <-> Matrix which was followed early by the CRAN packages zoo <-> xts upon which I built xts <-> RcppXts with a write-up (from 2013 !!) here: https://gallery.rcpp.org/articles/accessing-xts-api/ Via private mail, I helped then-maintainer Vincent connect expm: expm <-> Matrix and built two packages on CRAN _for the very purpose of exporting API functions to be called_ (which in both cases...

Dear all, in my package 'stochvol' I have unsuccessfully been trying to make a C routine called 'sampler' available to be called from other packages' C code. Following http://cran.r-project.org/doc/manuals/R-exts.html#Linking-to-native-routines-in-other-packages I have included #include <R_ext/Rdynload.h> R_init_stochvol(DllInfo *dll) {

Hi, I am trying to make a package B that extends another package A. Package A uses Rcpp, and I want to extend a class X used there. So package A has src/X.h and inst/include/X.h class X { ... } src/X.cpp X::X( arguments ) { ... } My package B wants to do this: DESCRIPTION [...] LinkingTo: Rcpp, RcppArmadillo, A Imports: Rcpp, RcppArmadillo, A src/Y.h class Y: public X { ... } src/Y.cpp