Re: [Json] Limitations on number size?

[Stephan Beal <[e-mail]>]

On Tue, Jul 9, 2013 at 3:26 PM, Peter F. Patel-Schneider <
[e-mail]> wrote:

> My informed understanding of JSON, from reading all the relevant
> documents, was (and again is) also that JSON numbers are ECMAScript numbers
> are IEEE floating point doubles (minus some odd bits).  I was astonished to
> find out that some people disagree, apparently to the point that they
> believe that 0 is different from .0
>

My (also informed) interpretation differs significantly ;). My last reading
of the RFC didn't reveal any mention of numeric precision. i.e. an
implementation which supports 5-bit precision is, from my reading of the
RFC, completely legal (it only has to be able to read a number with the
digits 0-9).


Not being clear on the primitive data types in JSON is a very bad thing, in
> my opinion.
>

It is impossible to require a specific precision because not all
platforms/environments can guaranty a specific precision.


> From: Jacob Davies <jacob at well.com>
> To: "json at ietf.org" <json at ietf.org>
> Date: Wed, 5 Jun 2013 10:51:58 -0700
>
> On Tue, Jun 4, 2013 at 9:05 PM, Nico Williams <nico at cryptonector.com>
> wrote:
> .,,Implementation limits on the length of strings or size of arrays or
> objects were not specified either
>


Which implies (to me) that a 5-bit-precision implementation is perfectly
legal (though obviously not very useful).

-- 
----- stephan beal
http://wanderinghorse.net/home/stephan/
http://gplus.to/sgbeal