Skip to content

Excluding objects from save.image

5 messages · Simon Urbanek, Tim Keitt

#
Tim,
On May 21, 2014, at 9:54 PM, Tim Keitt <tkeitt at utexas.edu> wrote:

            
than's not surprising - it's actually very useful, because it tells you that the object has been restored. Typically, packages using external pointers use this to re-inilitialize the object from serialized data or other sources if possible.
Why would you want to not save it? It exists, so saving it makes it possible to decide on the behavior as needed - as opposed to not saving it and thus losing the information.

Cheers,
Simon
#
On May 22, 2014, at 11:33 AM, Tim Keitt <tkeitt at utexas.edu> wrote:

            
Automatically - that is the point :).
Load time is typically not an issue, since you can just do it lazily. (Incidentally, doing that eagerly at load time is the hard part since you'd have to load the packages necessary in the right order which is not always possible to determine from the serialization alone. It's a full can of worms, because R doesn't know anything about sharing and dependencies on the native side etc.).

However, having a proper save hook for ext ptrs would be very useful. When I was asking for it few years ago, Luke mentioned there were issues - maybe it's something that could be re-visited.

Cheers,
Simon