On Tue, Sep 29, 2009 at 14:44, gus <gus / progress.com> wrote:
> On 9/29/09 2:14 PM, "Caleb Clausen" <caleb / inforadical.net> wrote:
>
>> Tim Bray wrote:
>>> Per RFC4267, http://www.ietf.org/rfc/rfc4627.txt, "foo" isn't legal JSO=
N.
>>> Top level has to be an object {} or array []. =A0So unparse should refu=
se to
>>> process "foo". =A0This isn't just a theoretical standards-wonk problem,=
 I got
>>> bitten trying to interop with Java JSON libraries on this one.
>>
>> Do you (or anyone else) have any idea why it was specified this way? It
>> seems kind of inconvenient.
>
> It is meant to be a subset of JavaScript and has to conform to the
> JavaScript spec.

I believe it is valid to have a free standing string literal in
JavaScript actually.

Brian.