This turned out to be nastier than expected, so it's good you pointed it
out.
The problem is not the serialized objects themselves, but the
restoration of the namespace, for package urca in your example.
Because the methods package had not been attached when the user data was
restored, the me
Dear John, Dear Seth,
many (a thousands) thanks for your clarification and highlighting of the
problem.
>It's not a simple serialization issue, but related to the initial
>computations when a saved image is reloaded at the start of a session,
>so the implication is less general than you imply.
It's not a simple serialization issue, but related to the initial
computations when a saved image is reloaded at the start of a session,
so the implication is less general than you imply.
If you move the saved image to another file, say "savedImage", then:
> load("savedImage")
> library(urca)
John Chambers <[EMAIL PROTECTED]> writes:
> I haven't had a chance to verify these exact examples, but the likely
> explanation is that loading the workspace does not cache the saved
> methods. Assuming this is indeed what's happening, the workaround is to
> cache them "manually" by the call:
I haven't had a chance to verify these exact examples, but the likely
explanation is that loading the workspace does not cache the saved
methods. Assuming this is indeed what's happening, the workaround is to
cache them "manually" by the call:
cacheMetaData(.GlobalEnv)
(after attaching the
Dear R-Devel subscriber,
as a follow up to my yesterday's email: I tested an analogous example
with the S4-package "flexclust" by executing the following code:
library(flexclust)
example(cclust)
cl
After saving the work space and starting a new R process with the
restored work space, the same be
