News for hackers. Stuff that matters.
Re:Unintuitive JSON Parsing by jchook on Saturday December 28, 2019 @04:41PM (#21901959)
That said, in theory, shouldn't:

JSON.parse("0o10") === 8?

I get SyntaxError: Unexpected token o in JSON at position 1

Re:Unintuitive JSON Parsing by ufedvjot13467 on Saturday December 28, 2019 @05:02PM (#21902095)
No. Valid json is valid JavaScript. Valid JavaScript is not, necessarily, valid json.
Re:Unintuitive JSON Parsing by jchook on Saturday December 28, 2019 @11:23PM (#21903937)
Thanks, I misunderstood the proposal, which apparently applies mostly to "unescaped LINE SEPARATOR or PARAGRAPH SEPARATOR characters" within strings.
Re:Unintuitive JSON Parsing by Jasper_ on Saturday December 28, 2019 @08:55PM (#21903309)
JSON.parse("(function() { })") doesn't parse either, despite being valid JavaScript. Both constructs are specific to JavaScript, and do not exist in JSON. Hence, JSON is a subset of JavaScript.