On Sunday, July 20, 2003, at 12:38 AM, Steven Frank wrote:
embeddable ECMAScript interpreter. I've made a little bit of progress
toward that end... Much to learn.
directly, as it does not have a stable API (or indeed, any public API
I'm wondering if there's an easy way to flatten out and save to disk
the current execution state of a KJS interpreter? In other words,
starting with the global object, just freeze-dry everything into a
flat file that can be loaded and re-animated later, with the script
environment picking up exactly where it left off.
I didn't see anything obvious in the docs or headers... Is it
possible? If so, how might one go about it?
You can freeze-dry the state of things using
KJS::Object::saveProperties() and KJS::Interpreter::saveBuiltins(),
enough that you can mostly restore the interpeter state later. We did
this for the back/forward cache support in WebCore. However this code
is probably not good enough if you want to serialize things to disk. It
does not save read-only properties or special properties implemented
directly in C++; it doesn't do a deep copy; and it doesn't let you
determine the true class of the object, or give you a way to
instantiate one yourself. It might be a helpful starting point for you,