IETF Logo Mail Archive

[Json] Numeric ECMAScript limitations

John Cowan <cowan@mercury.ccil.org> Sat, 22 June 2013 20:42 UTC

Return-Path: <cowan@ccil.org>
X-Original-To: json@ietfa.amsl.com
Delivered-To: json@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DE27721F9C22 for <json@ietfa.amsl.com>; Sat, 22 Jun 2013 13:42:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.452
X-Spam-Level:
X-Spam-Status: No, score=-3.452 tagged_above=-999 required=5 tests=[AWL=0.147, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id w2WcmDVlOBeb for <json@ietfa.amsl.com>; Sat, 22 Jun 2013 13:42:04 -0700 (PDT)
Received: from earth.ccil.org (earth.ccil.org [192.190.237.11]) by ietfa.amsl.com (Postfix) with ESMTP id 8BF1021F9BF9 for <json@ietf.org>; Sat, 22 Jun 2013 13:42:04 -0700 (PDT)
Received: from cowan by earth.ccil.org with local (Exim 4.72) (envelope-from <cowan@ccil.org>) id 1UqUdE-0001qY-3b; Sat, 22 Jun 2013 16:42:00 -0400
Date: Sat, 22 Jun 2013 16:42:00 -0400
From: John Cowan <cowan@mercury.ccil.org>
To: Nico Williams <nico@cryptonector.com>
Message-ID: <20130622204200.GT31186@mercury.ccil.org>
References: <05A7D2E5-C119-4900-B52B-54B0F1206300@lindenbergsoftware.com> <CA+mHimPF5Q4us+pUKnT79h6SbS63Qh7bAOkp4tSpaCvDWZf-2g@mail.gmail.com> <FB5408B8-68ED-4ACB-96DE-C3AD69240B10@lindenbergsoftware.com> <CAK3OfOhKc4PP7NHoTDce8KK-ZB01DEw=hCQLAZc+EyUjsD0tRw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <CAK3OfOhKc4PP7NHoTDce8KK-ZB01DEw=hCQLAZc+EyUjsD0tRw@mail.gmail.com>
User-Agent: Mutt/1.5.20 (2009-06-14)
Sender: John Cowan <cowan@ccil.org>
Cc: Norbert Lindenberg <ietf@lindenbergsoftware.com>, Stephen Dolan <stephen.dolan@cl.cam.ac.uk>, "json@ietf.org" <json@ietf.org>
Subject: [Json] Numeric ECMAScript limitations
X-BeenThere: json@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "JavaScript Object Notation \(JSON\) WG mailing list" <json.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/json>, <mailto:json-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/json>
List-Post: <mailto:json@ietf.org>
List-Help: <mailto:json-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/json>, <mailto:json-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 22 Jun 2013 20:42:09 -0000

Nico Williams scripsit:

> I don't think it's any more reasonable to require that parsers pass
> through any old non-Unicode string contents than it would be to require
> a specific range of real numbers to be passed by all parsers.

Right, that's another thing for the ECMAScript Stupid Tricks section:
ECMAscript JSON limits the range of numbers to the finite values of
64-bit IEEE floats, whereas RFC JSON has no fixed limitation, though it
licenses parsers to specify one.

-- 
John Cowan    cowan@ccil.org    http://ccil.org/~cowan
Objective consideration of contemporary phenomena compel the conclusion
that optimum or inadequate performance in the trend of competitive
activities exhibits no tendency to be commensurate with innate capacity,
but that a considerable element of the unpredictable must invariably be
taken into account. --Ecclesiastes 9:11, Orwell/Brown version

v2.23.0 | Report a Bug | By Email