Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:73164
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.219.54 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CAMauByVH=UShnTLEZrOBSs2nANSQ9R4pVCbYBvyXXvzz51gMTw@mail.gmail.com>
References: <CAEKnhAEFCALpqA8_Gsr-TH_4GUmscrGhLRD70VcAFFV3ij68PQ@mail.gmail.com>
	<CAMauByVH=UShnTLEZrOBSs2nANSQ9R4pVCbYBvyXXvzz51gMTw@mail.gmail.com>
Date: Fri, 14 Mar 2014 08:12:24 -0600
Message-ID: <CAFMT4NrgoWEtRn_5GE4B8xXg9-20kPSwTMkPyhjqgkHb1hTy2A@mail.gmail.com>
To: Marco Schuster <marco+php@m-s-d.eu>
Cc: Jakub Zelenka <bukka@php.net>, PHP internals list <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=e89a8ff25042b8480f04f491a88f
Subject: Re: [PHP-DEV] New JSON parser
From: morrison.levi@gmail.com (Levi Morrison)

--e89a8ff25042b8480f04f491a88f
Content-Type: text/plain; charset=ISO-8859-1

>
> > 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 also oppose these proposals.


> 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.
>

This is a problem, I agree.

--e89a8ff25042b8480f04f491a88f--