I think you're right, the ecma 404 spec changed from prior versions of RFCs, although I've run into many parser implementations that go off the older specifications that had the "A JSON text is a serialized object or array." bit in them.
On Tuesday, January 7, 2014 10:47:58 PM UTC-7, Sander Elias wrote: > > Hi Daniel, > > Can you point me to that section? I could not find it on JSON.org neighter > in the ecma 404 > spec<http://www.ecma-international.org/publications/files/ECMA-ST/ECMA-404.pdf>. > > (that name still cracks me up ;) ) I just read the json rfc (wasn't aware > of that one!) and it is indeed stated in there. > Still, the rfc isn't the formal standard, the ecma 404 is, and in there > it's not! So, formally speaking, it *is technically correct. * > however I do think it's a bad idea to use it like that! and most parsers > don't parse it correctly! > > Regards > Sander > > > > > -- You received this message because you are subscribed to the Google Groups "AngularJS" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/angular. For more options, visit https://groups.google.com/groups/opt_out.
