undefined | Better HN

0 pointszeroimpl1y ago0 comments

Example? I know there's some ambiguity over whether literals like false are valid JSON, but I can't think of anything else.

0 comments

4 comments · 2 top-level

recursive1y ago· 2 in thread

Trailing commas, comments, duplicate key names, for a few examples.

int_19h1y ago

Trailing commas and comments are plainly not standard JSON under any definition. There are standards that include them which extend JSON, sure, but I'm not aware of any JSON library that emits this kind of stuff by default.

recursive1y ago

I'm not aware of any CSV library that doesn't follow RFC4180 by default, and yet... this whole thread.

tubthumper81y ago

That _shouldn't_ be ambiguous, `false` is a valid JSON document according to specification, but not all parsers are compliant.

There's some interesting examples of ambiguities here: https://seriot.ch/projects/parsing_json.html

j / k navigate · click thread line to collapse