That's correct (json.org) doesn't show comment as valid part of JSON description. I added key: list form to the doc.
2009/6/30 Mark Miller <[email protected]> > On Tue, Jun 30, 2009 at 3:44 PM, Nebojša Ćirić <[email protected]> wrote: > >> >> >> Most frameworks do that by using native comments. We could extend JSON with: >> { >> "greeting": [ "hallo!", "Greeting message" ], >> "exit": [ "goodbye", "Going away message"], >> } >> >> or just say: >> { >> // Greeting message. >> "greeting": "hallo!", >> // Going away message. >> "exit": "goodbye" >> } >> >>> > The first is valid JSON. The second is not. A conforming JSON parser may > reject it. A validating JSON parser must reject it. I believe ES5 mandates a > validating parser. > > > -- > Text by me above is hereby placed in the public domain > > Cheers, > --MarkM > > > > > > --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
