Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:80374
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.213.177 as permitted sender)
MIME-Version: 1.0
Sender: jakub.php@gmail.com
Date: Sun, 11 Jan 2015 17:27:35 +0000
Message-ID: <CAEKnhAFvQpPxkoZKJ-2A-Fjm_ABqxPNMuJoqOsby3ELZgoyQ9g@mail.gmail.com>
To: PHP internals list <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=001a1141d074aa1078050c63b414
Subject: [RFC] jsond
From: bukka@php.net (Jakub Zelenka)

--001a1141d074aa1078050c63b414
Content-Type: text/plain; charset=UTF-8

Hi,

This rfc about replacing json with jsond is under discussion.

https://wiki.php.net/rfc/jsond

I have finally done some benchmarks. You can find a link in the RFC.

It's been extensively tested for the last few months and there is just one
BC that I'm aware of.

The new parser accepts only float number that conforms to RFC 7159 . This
is also not consistent between decoding float number that are and are not
in the array/object ( there are two conversion rules). The following
formats are rejected:

1. parsed at the top level: 07, 0xff, .1, -.1
2. parser by JSON_Parser: [1.], [1.e1]

I feel that this was a bug in the new parser and we must conform to RFC
7159 !

Cheers

Jakub

--001a1141d074aa1078050c63b414--