On Tue, Jan 10, 2012 at 6:17 AM, Simon Urbanek <simon.urba...@r-project.org> wrote: > Unfortunately R doesn't provide a way for this. Without changes to > unserialization (on the wishlist for a few years now, but not easy to design) > the best you can do is to check the native symbols for NULL pointers on usage > and then re-fetch - that's something that could be done reasonably easily, > although it's still a hack ...
Hmm that concerns me a bit. I make heavy use of saveRDS and readRDS in my framework and have assumed that for all practical purposes most objects can be saved to disk and loaded later on without problems. Are there any other types of objects that are not being serialized-unserialized to a state where they are functional again? In the case of the NativeSymbolInfo object, it should not be too hard to add an optional feature to unserialize which reloads the package and NativeSymbolInfo when it runs into nullpointers during unserialization? I am currently doing this manually after the unserialization, but that introduces quite some overhead. Thanks, Jeroen ______________________________________________ R-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-devel
