Re: [Json] JSON irritants

[John Cowan <[e-mail]>]

Wendy Roome scripsit:

> An optional final comma would be very convenient. But I think optional
> separator commas, with some rule to impute a comma at the end of a line,
> is a bad idea. Suppose the json runs thru a compressor that automagically
> squeezes out unnecessary white space. The result would be illegal unless
> the compressor understood the new rules.

If it didn't understand the new rules, it wouldn't accept [1 2 3] or
{"foo":"bar" "baz":"zam"} in the first place, so I don't think that's
a separate problem.

> For example, think about the number of time you write <tag /> instead of
> <tag/>, because some early xml parser didn't handle the latter properly.

Actually, it's older HTML parsers that had that problem, not XML ones.
Empty-tags didn't exist when HTML was derived from SGML.

-- 
John Cowan          http://www.ccil.org/~cowan        [e-mail]
There is no real going back.  Though I may come to the Shire, it will
not seem the same; for I shall not be the same.  I am wounded with
knife, sting, and tooth, and a long burden.  Where shall I find rest?
                --Frodo