these values make their
way onto the network.
--- 15.12 JSON
I'll send separate feedback on this section, but the July 4th draft
does not appear to match the most recent copy of json2.js. What's
going on here?
--
Robert Sayre
I would have written a shorter letter, but I did not have the time
with the old one. Happen to have one?
--
Robert Sayre
I would have written a shorter letter, but I did not have the time.
___
Es4-discuss mailing list
Es4-discuss@mozilla.org
https://mail.mozilla.org/listinfo/es4-discuss
2008/3/31 Nathan de Vries [EMAIL PROTECTED]:
Without being part of a standard such as ES4...
It is a library problem. The ES4 language spec is not the place to fix
every standard library deficiency.
--
Robert Sayre
I would have written a shorter letter, but I did not have the time
.
No doubt the WG has attitude. There are strong personalities involved and we
have had our share of knocks. Sometimes that shows.
It can probably show less if everyone makes an effort. The WG has most
of the implementors one could hope for, so this opportunity shouldn't
be wasted.
--
Robert Sayre
I
On Thu, Feb 21, 2008 at 3:48 PM, Geoffrey Garen [EMAIL PROTECTED] wrote:
However, since there is no spec -- at least, not one I can lay my
hands on -- I'll have to wait until the people in the know finish
their implementations
What changes would you like to see in the process? What would
too __, where the blank is some
subjective quality. This one is longer, with a calmer tone, but I
still don't see much substance. If the language is as radical and
complicated departure as you say it is, it should be easy to find bugs
in the design.
--
Robert Sayre
I would have written
and another object returns a compensating
unbalanced string, then an outer toJSONString() can
produce quoting confusions that invite XSS-like
attacks. The primary purpose of safe-json.js is to
prevent such attacks.
--
Robert Sayre
I would have written
