[Rcpp-devel] R.e. loadRcppModules

Christian Gunning xian at unm.edu
Wed Apr 13 07:29:58 CEST 2011

On Tue, Apr 12, 2011 at 7:06 AM, Douglas Bates <bates at stat.wisc.edu> wrote:
> The documented behavior is that an external pointer is replaced by a
> null pointer when an object is serialized.

Thanks. Got it.

> I was planning to
> experiment with an object that has enough information saved as R
> objects to be able to regenerate the C++ object and an external
> pointer to the module instance.  The methods that use the object will
> check first to see if the pointer is null, in which case they will
> regenerate the module instance, otherwise go directly to invoking
> methods on the module instance.

No rush on my part -- as usual, I'm just trying to figure out how the
pieces fit together :)

Just to clarify --  does your plan include storing user-modified
fields and properties in objects?  E.g. below, modtest with the msg


Rcpp.package.skeleton('testpkg1', module=T)
modtest <- new(World)

A man, a plan, a cat, a ham, a yak, a yam, a hat, a canal – Panama!

More information about the Rcpp-devel mailing list