Crockford thought that you could avoid version impedance mismatches by not versioning things. This doesn't work! https://www.computer.org/csdl/mags/co/2012/04/mco2012040006.html …pic.twitter.com/tShrqyoR3G
-
Are there spec-compliant JSON documents that don't parse in some parsers (modulo genuine bugs)?
What's a bug? :) What should happen when you pass a "big" number in JSON? 1. Reject 2. FP Infinity 3. Round 4. BigInt 5. BigFloat
-
-
(1) is arguably a bug by original spec, but RFC 7159 says "An implementation may set limits on the range and precision of numbers"
-
OTOH it also says "A JSON parser MUST accept all texts that conform to the JSON grammar"; maybe you're supposed to accept and do 2-5?
End of conversation
New conversation -
-
-
I think any of 2-5 is allowed. JSON defines a syntax but not a semantics.
-
More importantly, this isn't fixable by versioning. A new version of JSON couldn't make JS/Racket/Java have the same number system.
- 2 more replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.