On Jun 6, 2013, at 6:46 AM, Rick Waldron wrote: > > > > On Thu, Jun 6, 2013 at 7:29 AM, Douglas Crockford <[email protected]> > wrote: > The JSON RFC says > > The names within an object SHOULD be unique. > > Sadly, there are people in the JavaScript community who interpreted SHOULD to > mean DON'T HAVE TO. In a perfect world, we would change the SHOULD to MUST, > but we can't. Interoperability and security concerns demand that we specify > what happens when keys are duplicated. So we may end up with something like > this: > > The names within an object SHOULD be unique. If a key is duplicated, > a parser SHOULD reject. If it does not reject, it MUST take only the > last of the duplicated key pairs. > > +1 > > As far as I can tell, this is the de facto browser behavior.
I'm not sure what you mean by this. The ES5 spec. for JSON.parse requires (ie MUST accept) that duplicate keys are accepted and that the value associated with the last duplicated key wins. A valid implementation of JSON.parse MUST not reject such JSON strings. Allen
_______________________________________________ es-discuss mailing list [email protected] https://mail.mozilla.org/listinfo/es-discuss
