Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:73134
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain m-s-d.eu from 209.85.223.173 cause and error)
MIME-Version: 1.0
Sender: marco@m-s-d.eu
In-Reply-To: <CAEKnhAEFCALpqA8_Gsr-TH_4GUmscrGhLRD70VcAFFV3ij68PQ@mail.gmail.com>
References: <CAEKnhAEFCALpqA8_Gsr-TH_4GUmscrGhLRD70VcAFFV3ij68PQ@mail.gmail.com>
Date: Thu, 13 Mar 2014 23:37:54 +0100
Message-ID: <CAMauByVH=UShnTLEZrOBSs2nANSQ9R4pVCbYBvyXXvzz51gMTw@mail.gmail.com>
To: Jakub Zelenka <bukka@php.net>
Cc: PHP internals list <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Subject: Re: [PHP-DEV] New JSON parser
From: marco+php@m-s-d.eu (Marco Schuster)

Hi,

On Thu, Mar 13, 2014 at 8:48 PM, Jakub Zelenka <bukka@php.net> wrote:
> I need to do more testing before creating RFC for replacing the current
> parser. There is still space for further improvements. If anyone has any
> ideas, please let me know. Or if you could test it, that would be great
> too! ;)

At least for the decoding part, it might be worth to look at the
"Improving JSON" proposal (http://bolinfest.com/essays/json.html).
tl;dr: support trailing or automatic line-end commas, //-style
comments and keys not wrapped in "s, basically extend JSON syntax to
ES5.

I think it would be really cool if the new parser could (maybe with a
option "JSON_NO_STRICT_PARSING") implement these enhancements to ease
hand-writing of JSON files.

Also, will end-users be able to get the JSON parser error message?
Currently, all you get is a NULL returned when you have a parse error
somewhere in your JSON - and it's a nightmare to debug with this.

Marco