Just Write the Parser

Re:Just Write the Parser by eyelidlessness on Wednesday October 21, 2020 @06:15PM (#24852831)

Considering that something as simple and limited as JSON has been a source of security vulnerabilities from ambiguities in the spec, thanks but nope. Declarative definitions of a grammar help identify those ambiguities... and if the grammar is defined separately from its interpretation, it opens the door to invisible ambiguities that can become another vector for vulnerabilities.

Unless you have provable implementations (great if you do!), declarative grammars meaningfully limit points of failure.

[ Parent | on HN ]

Re:Just Write the Parser by lifthrasiir on Thursday October 22, 2020 @12:59AM (#24855028)

Spec ambiguities of JSON mostly come from the insufficient description of data model and well-formedness and not from the syntax itself. Say, to this day (including RFC 8259) duplicate keys from the JSON object are not explicitly forbidden, even though most applications require that. Probably the only issue arisen from the JSON syntax proper would be the treatment of line and paragraph separators.

[ Parent | on HN ]

Re:Just Write the Parser by sleavey on Thursday October 22, 2020 @11:43AM (#24859237)

And my number one gripe, that you can't add a trailing comma to the last list item. Very annoying when streaming JSON data.

[ Parent | on HN ]