Subj : Re: [SpiderMonkey] Serializing JSObject
To   : netscape.public.mozilla.jseng
From : ggadwa@charter.net
Date : Wed Jun 23 2004 06:25 pm

Brendan Eich wrote:

> No, I meant it requires knowledge of JSClass-specific private data, 
> other JSObjectOps variations on object structure, and in general, 
> issues to do with scope chain and other runtime parameters.

Shouldn't be a problem -- I'm backing up and object that lives within a 
script, and the object I'm backing up is all generated from within the 
script -- so all the ops and private data shouldn't exist.  As I said 
before, it's a system that's designed to support only a certain subset.  
More or less, I'm capturing the globals of a script, nothing else.  Then 
recreating them after I relaunch the script.  I should be pretty cool here.

> This sounds awfully like uneval and eval to me. 

Wouldn't they have the same problems you noted above? I'll take a look, 
this isn't anything I noticed because it's not in the docs.  Care to 
explain these a bit further?  Are we talking about the eval in 
javascript itself?  All this happens in my C code, behind the scenes.

If there's a simple function I can call on a JSObject that can covert it 
back and forth from a string, I'm all for it, even though creating the 
code is fun :)

[>] Brian

.