4 ms·

Ah fair enough on the break, I was wrong there. But if the spec says that keys SHOULD be unique, what's the behaviour when they aren't?

• dnautics 13y ago
  I would agree it's very hackey and probably not a good idea since the spec is liable to change. But I wouldn't be sad if the spec were changed to allow for this, or to allow for comments.
  • IanCal 13y ago
    > I would agree it's very hackey and probably not a good idea since the spec is liable to change Well it's not really about the spec changing, the spec doesn't have a defined behaviour for duplicate keys. > But I wouldn't be sad if the spec were changed to allow for this, or to allow for comments. I don't think duplicate keys should be allowed, but I've no strong feelings on comments. I don't think there's any real need for them though.
    • dnautics 13y ago
      I'm biased, back in the BeOS -> Haiku days, I was wanting some sort of configuration textfile that would neatly be able to be parsed into a BArchive object (and presumably transmitted into a BMessage). XML was all the rage at the time, so I wrote for myself a sort of XML-ish format, but I never contributed it to the tree. I learned the problems with XMLs (should it be an attribute or an innerText?). I wanted something with a bracket notation, but JSON had not been discovered by crockford yet, if it had been I would have gotten more involved and tried to have it be adopted.