News for hackers. Stuff that matters.

A comment on Parsing JSON Is a Minefield (2016). Parent comment

Re:Parsing JSON Is a Minefield (2016) by josefx on Monday October 11, 2021 @05:51PM (#28833515)
> To the point that I don't understand why it was left out of JSON

Because JSON has generic numbers that just happen to be able to represent every numeric IEEE floating point double value. In theory you could have an implementation that uses a BigDecimal class or something similar to represent numeric values. Which is of course completely incompatible with every other JSON implementation and just asks for badly tested edge cases to rear their ugly head.

[ Parent | on HN ]
Re:Parsing JSON Is a Minefield (2016) by stinos on Tuesday October 12, 2021 @02:02AM (#28836569)
every numeric IEEE floating point double value

Well, but not NaN and Inf? Or which IEEE are you referring to?

[ Parent | on HN ]
Re:Parsing JSON Is a Minefield (2016) by josefx on Tuesday October 12, 2021 @04:42AM (#28837463)
NaN and Inf are not numbers.
[ Parent | on HN ]