Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:80380
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain ajf.me designates 192.64.116.207 as permitted sender)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 8.1 \(1993\))
In-Reply-To: <CAEKnhAHrTYUqxNVrKTUY8snMJ2in6WLZ9YPg2tfcMSns0N-hFw@mail.gmail.com>
Date: Sun, 11 Jan 2015 21:19:44 +0000
Cc: Paul Dragoonis <dragoonis@gmail.com>,
 PHP Internals List <internals@lists.php.net>
Content-Transfer-Encoding: quoted-printable
Message-ID: <B748EBE8-12AA-4E10-899A-1EF0EE4B11EF@ajf.me>
References: <CAEKnhAFvQpPxkoZKJ-2A-Fjm_ABqxPNMuJoqOsby3ELZgoyQ9g@mail.gmail.com> <CAKxcST_e44EEXj7AuXm0xiXhNmfqjc6uCFRxD4bw6DFycNVy8A@mail.gmail.com> <CAEKnhAHrTYUqxNVrKTUY8snMJ2in6WLZ9YPg2tfcMSns0N-hFw@mail.gmail.com>
To: Jakub Zelenka <bukka@php.net>
Subject: Re: [PHP-DEV] [RFC] jsond
From: ajf@ajf.me (Andrea Faulds)

Hey Jakub,

> On 11 Jan 2015, at 20:10, Jakub Zelenka <bukka@php.net> wrote:
>=20
> Let's first show an example and make clear what the whole thing:
> http://3v4l.org/2D72Q
>=20
> As you can see, the first type (07, 0xff, .1 and -.1) examples are =
really
> inconsistent and give a different results if there are in the array =
(error)
> or as a scalar. This seems like an obvious bug.
>=20
> The type 2 is consistent. The only problem is that such number format =
does
> not conform to RFC 7159 where the number is specified in
> https://tools.ietf.org/html/rfc7159#section-6 :
>=20
>    number =3D [ minus ] int [ frac ] [ exp ]
>    frac =3D decimal-point 1*DIGIT
>=20
> As you can see there is required a digit after decimal point... In =
this
> case we have a non conforming parser which is not right IMHO.

It=E2=80=99s not even valid according to the train-track diagrams on =
json.org:

    http://json.org/number.gif

Thanks for your work on this.
--
Andrea Faulds
http://ajf.me/