Re: [Rcpp-devel] Rcpp modules and return_value_policy for exposed C++ member functions

On 10 November 2014 at 16:51, Claymore Marshall wrote: | Thank you for the feedback Dirk.  Fair enough. | | I think the issue I have is similar to this (I want to set  StoragePolicy = | false for the XPtr), so I sort of have a work around going: http:// | lists.r-forge.r-project.org/pipermail/rcp

Re: [Rcpp-devel] Rcpp modules and return_value_policy for exposed C++ member functions

Thank you for the feedback Dirk. Fair enough. I think the issue I have is similar to this (I want to set StoragePolicy = false for the XPtr), so I sort of have a work around going: *http://lists.r-forge.r-project.org/pipermail/rcpp-devel/2013-February/005273.html

Re: [Rcpp-devel] Rcpp modules and return_value_policy for exposed C++ member functions

On 10 November 2014 at 13:16, Claymore Marshall wrote: | I want to expose to R several C++ classes from a library with Rcpp modules.  | I'm trying to imitate a similar set of Python modules that were made for the | same library. | | In Boost.Python, with .def it is possible to specify the return_

[Rcpp-devel] Rcpp modules and return_value_policy for exposed C++ member functions

I want to expose to R several C++ classes from a library with Rcpp modules. I'm trying to imitate a similar set of Python modules that were made for the same library. In Boost.Python, with .def it is possible to specify the return_value_policy. Is it also possible to do this in a straight forwar