Hi Troy, Glad to hear you're covered.
On 21 March 2012 at 07:45, Troy Robertson wrote: | Hi Dirk, | | It's okay. I just created my own copy of the setCMethod and added the | missing ellipses to it's call to cfunction() and it works fine. | It now passes on the Rcpp=TRUE and the cppargs and libargs and finds | both the Rcpp and my own library. That's how we started too, prior to cxxfunction(). I am wondering if I could interest you in looking at the cxxfunction code maybe thinking about extending to whichever form it takes to let you create S4 methods that way. Any interest? Cheers, Dirk | | Troy | | On 21/03/2012 12:19 AM, Dirk Eddelbuettel wrote: | > On 19 March 2012 at 14:32, Troy Robertson wrote: | > | Okay, after having a look at the source for the inline package, I see | > | that ... arguments to setCMethod() | > | are not passed on in its internal call to cfunction(), hence my cppargs | > | and libargs (and indeed Rcpp=TRUE) | > | are ignored? | > | > As I said before, we extended the inline package with cxxfunction() for use | > with Rcpp et al, and essentially only use cxxfunction. | > | > As for S4 methods, there are some example tucked away in the unittests you | > could look at. | > | > For the rest, I am not entirely clear as to what it is you want to do. Maybe | > Rcpp modules could help you, though it is closer to Reference Classes than to | > S4 classes. | > | > Hoep this helps, Dirk | > -- "Outside of a dog, a book is a man's best friend. Inside of a dog, it is too dark to read." -- Groucho Marx _______________________________________________ Rcpp-devel mailing list [email protected] https://lists.r-forge.r-project.org/cgi-bin/mailman/listinfo/rcpp-devel
