Re: [Json] Limitations on number size?

[Jorge Chamorro <[e-mail]>]

On 09/07/2013, at 23:24, Peter F. Patel-Schneider wrote:
> 
> Imagine my surprise when I was told that my reasoning was not correct.

A "JSON number" is a *text* not a number:

number = [ minus ] int [ frac ] [ exp ]

         decimal-point = %x2E       ; .

         digit1-9 = %x31-39         ; 1-9

         e = %x65 / %x45            ; e E

         exp = e [ minus / plus ] 1*DIGIT

         frac = decimal-point 1*DIGIT

         int = zero / ( digit1-9 *DIGIT )

         minus = %x2D               ; -

         plus = %x2B                ; +

         zero = %x30                ; 0

A character representation of a number that follows the rules in the RFC 4627 that -unlike ECMAScript- doesn't say a thing about its precision, integer-ness, floating-point-ness, allowable ranges or the likes.


To say that a "JSON number" (which is a text) is === IEEE-754 double doesn't make too much sense.


JSON.stringify(number:number) -> text:JSON_number
JSON.parse(text:JSON_number)  -> number:number
-- 
( Jorge )();