9182 2006-05-31 02:34:35 -0700 Add support for toSource and/or uneval 2009-07-07 22:49:29 -0700 1 1 1 Unclassified WebKit JavaScriptCore 420+ Mac OS X 10.4 RESOLVED FIXED P2 Enhancement --- 1 jruderman webkit-unassigned emacemac7 gavin.sharp ian mike mjs mrowe oliver oldest_to_newest 44099 0 jruderman 2006-05-31 02:34:35 -0700 Firefox's toString and uneval are pretty handy. It would be nice if I could use them in WebKit, instead of having to serialize strings and objects manually when I want to port something from Gecko to WebKit. uneval("foo") --> "\"foo\"" uneval({a:1}) --> "({a:1})" I'm not sure if uneval and toSource are the same. I have the feeling they're not. 10532 1 jruderman 2007-05-09 18:22:45 -0700 I of course meant "toSource", not "toString". 68184 2 oliver 2008-01-24 20:48:58 -0800 This makes it easier to run jsfunfuzz https://bugzilla.mozilla.org/attachment.cgi?id=240710 68185 3 oliver 2008-01-24 20:54:55 -0800 Hmm, some digging would appear to indicate there is no way to define a self referencing parameter in json :-/ eg. a=[]; a[0]=a; uneval(a); or at a greater extreme: a = {b:{c:a}}; a.c = a.b.c; uneval(a); 130372 4 oliver 2009-07-07 22:49:29 -0700 We support JSON.stringify now which is basically what was being requested