Re: [Rcpp-devel] Resolving NativeSymbolInfos from Rcpp (revisited)

2017-07-29 Thread Iñaki Úcar
One last question: would you consider adding a cppXPtr() function to Rcpp? It would work as cppFunction(), but it would return a XPtr instead of the function. I have a working example if you are interested. Iñaki ___ Rcpp-devel mailing list Rcpp-devel@li

Re: [Rcpp-devel] Resolving NativeSymbolInfos from Rcpp (revisited)

2017-07-29 Thread Iñaki Úcar
2017-07-29 16:15 GMT+02:00 Dirk Eddelbuettel : > > On 29 July 2017 at 15:48, Iñaki Úcar wrote: > | Yes, I am, and I think that my use case is slightly different. My > | understanding is, correct me if I'm wrong, that RcppDE implements some > | C++ functions and the user is able to choose which one

Re: [Rcpp-devel] Resolving NativeSymbolInfos from Rcpp (revisited)

2017-07-29 Thread Dirk Eddelbuettel
On 29 July 2017 at 15:48, Iñaki Úcar wrote: | Yes, I am, and I think that my use case is slightly different. My | understanding is, correct me if I'm wrong, that RcppDE implements some | C++ functions and the user is able to choose which one the backend | should use via its name. In my case, the u

Re: [Rcpp-devel] Resolving NativeSymbolInfos from Rcpp (revisited)

2017-07-29 Thread Iñaki Úcar
2017-07-29 15:02 GMT+02:00 Sokol Serguei : > Jj Allaire has written at Sat, 29 Jul 2017 07:58:13 -0400 > > The best you can do is to get the pointer to the function (not sure if that > does what you are hoping for): > > func <- Rcpp::cppFunction("int foo() { return 1; }") > >> body(func) > .Primit

Re: [Rcpp-devel] Resolving NativeSymbolInfos from Rcpp (revisited)

2017-07-29 Thread Dirk Eddelbuettel
On 29 July 2017 at 15:00, Iñaki Úcar wrote: | With our simulator, simmer, we are able to generate arrivals, entities | that execute a given set of activities. One of these activities could | be, let's say, a delay. A user can provide this delay as a fixed | parameter to the C++ core, but also as a

Re: [Rcpp-devel] return Colvec as vector

2017-07-29 Thread Dirk Eddelbuettel
On 29 July 2017 at 01:47, Sokol Serguei wrote: | Dirk Eddelbuettel has written at Fri, 28 Jul 2017 17:28:11 -0500 | > On 28 July 2017 at 14:59, Serguei Sokol wrote: | > | Le 28/07/2017 à 13:45, Dirk Eddelbuettel a écrit : | > | > Don't think so, but I have thought about it too, and I was planning

Re: [Rcpp-devel] Resolving NativeSymbolInfos from Rcpp (revisited)

2017-07-29 Thread Sokol Serguei
Jj Allaire has written at Sat, 29 Jul 2017 07:58:13 -0400 The best you can do is to get the pointer to the function (not sure if that does what you are hoping for): func <- Rcpp::cppFunction("int foo() { return 1; }") > body(func) .Primitive(".Call")() And to narrow even more: > Rcpp::cppFun

Re: [Rcpp-devel] Resolving NativeSymbolInfos from Rcpp (revisited)

2017-07-29 Thread Iñaki Úcar
2017-07-29 13:58 GMT+02:00 JJ Allaire : > The best you can do is to get the pointer to the function (not sure if that > does what you are hoping for): > > func <- Rcpp::cppFunction("int foo() { return 1; }") > >> body(func) > .Primitive(".Call")() I don't think so. Let me explain the motivation be

Re: [Rcpp-devel] Resolving NativeSymbolInfos from Rcpp (revisited)

2017-07-29 Thread JJ Allaire
The best you can do is to get the pointer to the function (not sure if that does what you are hoping for): func <- Rcpp::cppFunction("int foo() { return 1; }") > body(func) .Primitive(".Call")() On Fri, Jul 28, 2017 at 8:00 PM, Iñaki Úcar wrote: > 2017-07-29 0:29 GMT+02:00 Dirk Eddelbuettel :

Re: [Rcpp-devel] return Colvec as vector

2017-07-29 Thread Sokol Serguei
Dirk Eddelbuettel has written at Fri, 28 Jul 2017 17:28:11 -0500 On 28 July 2017 at 14:59, Serguei Sokol wrote: | Le 28/07/2017 à 13:45, Dirk Eddelbuettel a écrit : | > Don't think so, but I have thought about it too, and I was planning to bring | > this up. I also find the 'always forced to be