awwright

6 ms·

1.
by awwright 1y ago
Isn't that itself just a variation on the ini syntax, sort of made concrete by PHP, itself adapted from DOS? https://www.php.net/parse_ini_file
2.
by awwright 4y ago
I think what you're getting hung up on is that JSON does not use IEEE floating point math. If your implementation or environment stores parsed numbers as an IEEE floating point, that's a limitation the implementation has to disclo
3.
by awwright 4y ago
The behavior is perfectly well defined... there's no special cases for integers vs. rational numbers, they're all the same. For example, given multipleOf: 0.3, and an input of 0.9, 0.9/0.3 is 3, which is an integer, so would
4.
by awwright 4y ago
This is wrong. All numbers in JSON are arbitrary-precision base-10 decimal numbers.
5.
by awwright 4y ago
It does. In fact, not only does JSON support big ints, but it supports arbitrary-precision base-10 decimal numbers. Whether your JSON parser will preserve the precision correctly is another story. For JavaScript/ECMAScript, you'll
6.
by awwright 4y ago
Two corrections: (1) This is a good overview, but conservatives don't believe in the status quo for the status quo's sake. They believe that our traditions are highly optimized, essential components to living a fulfilling life. We
7.
by awwright 7y ago
It seems like there's two slight misunderstandings: > "oneOf": [ {"type": "number"}, {"type": "number"} ] > { "oneOf": [ {"minimum": 0, "maximum": 10
8.
by awwright 7y ago
How is that simple? What does "status" mean? I'm personally familiar with the word "status"—but whatever that property is, I'd have to re-implement it in my user agent, which seems like a waste because my user