On Wed, Sep 21, 2011 at 8:27 PM, Don Owens <don@...
> length? I don't think the JSON spec puts a limit on the size of an integer.
It specifies neither a limit nor a minimum, at least as far as i was able to
dig out of the RFC a few months ago. A 2-bit limit is, strictly speaking,
> If there is no way to encode large integers in your spec, people will
> invent their own way of doing it -- it's better to have a standard way of
If they're concerned with JSON and its portability they'll "probably" (i
doesn't separate int/double, and instead has a Number type with at least 53
significant bits. In my own code i use JSON doubles in lieu of int64, which
avoids the immediate incompatibility but probably also has range-related
overflow/underflow issues when using "really, really large" values (which my
uses cases haven't called for so far).
----- stephan beal
[Non-text portions of this message have been removed]