[whatwg] JSON encoding

Alfonso Baqueiro abaqueiro at gmail.com
Sat Nov 4 11:53:12 PST 2006

Here is the document that explains prototype.js and its extensions


2006/11/4, Ian Hickson <ian at hixie.ch>:
> (I couldn't work out what thread this was a continuation to -- the first
> message below didn't have a "Re:" in the subject line, and I can't find
> any other thread that used the word "hazard". So I don't know exactly
> what this thread was about. However, I shall not let that stop me from
> jumping in and giving my two cents...)
> On Fri, 3 Nov 2006, Douglas Crockford wrote:
> >
> > This is a convenience issue. Having toJSONString as a builtin is a
> > convenience, removing the need to load json.js.
> Assuming the thread is about introducing a way to convert a JS object into
> a JSON representation, then I would encourage you to contact the
> ECMAScript committee. Adding features to JavaScript is out of scope for
> the WHATWG specs.
> --
> Ian Hickson               U+1047E                )\._.,--....,'``.    fL
> http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
> Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.whatwg.org/pipermail/whatwg-whatwg.org/attachments/20061104/efa7b208/attachment-0001.htm>

More information about the whatwg mailing list