News for hackers. Stuff that matters.

A comment on A love letter to the CSV format. Parent comment

Re:A love letter to the CSV format by zeroimpl on Wednesday March 26, 2025 @07:49PM (#43488873)
Example? I know there's some ambiguity over whether literals like false are valid JSON, but I can't think of anything else.
[ Parent | on HN ]
Re:A love letter to the CSV format by tubthumper8 on Wednesday March 26, 2025 @09:41PM (#43489577)
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

[ Parent | on HN ]
Re:A love letter to the CSV format by recursive on Thursday March 27, 2025 @03:48PM (#43497381)
Trailing commas, comments, duplicate key names, for a few examples.
[ Parent | on HN ]
Re:A love letter to the CSV format by int_19h on Thursday March 27, 2025 @06:10PM (#43498771)
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.
[ Parent | on HN ]
Re:A love letter to the CSV format by recursive on Thursday March 27, 2025 @06:16PM (#43498823)
I'm not aware of any CSV library that doesn't follow RFC4180 by default, and yet... this whole thread.
[ Parent | on HN ]