Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:73138
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.213.177 cause and error)
MIME-Version: 1.0
Sender: marco@m-s-d.eu
In-Reply-To: <8C0E8F2C-4264-4B19-A9DD-67302A39F4CC@ajf.me>
References: <CAEKnhAEFCALpqA8_Gsr-TH_4GUmscrGhLRD70VcAFFV3ij68PQ@mail.gmail.com>
	<CAMauByVH=UShnTLEZrOBSs2nANSQ9R4pVCbYBvyXXvzz51gMTw@mail.gmail.com>
	<8C0E8F2C-4264-4B19-A9DD-67302A39F4CC@ajf.me>
Date: Fri, 14 Mar 2014 00:37:54 +0100
Message-ID: <CAMauByUhYLds3mY+UBzCL66XZVJT+BY5E0g3yAq46jB09R0HMw@mail.gmail.com>
To: Andrea Faulds <ajf@ajf.me>
Cc: Jakub Zelenka <bukka@php.net>, PHP internals list <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] New JSON parser
From: marco+php@m-s-d.eu (Marco Schuster)

Hi,

On Thu, Mar 13, 2014 at 11:52 PM, Andrea Faulds <ajf@ajf.me> wrote:
>
> On 13 Mar 2014, at 22:37, Marco Schuster <marco+php@m-s-d.eu> wrote:
>
> 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.
>
>
> Please, I urge you *not* to implement anything except the pure JSON
> standard. One of JSON=E2=80=99s great strengths is that there is only a s=
ingle,
> canonical JSON standard. Implementing other standards would be damaging t=
o
> interoperability.
Nothing is set in stone, and evolution should be allowed, especially
where it makes sense (trailing comma!). Also, that's why I suggested a
"relaxed parsing" flag. This way, people knowing the differences can
use what suits them best. (Also, IIRC there already exist polyfills to
implement this syntax).

> If people want nice config files, they can use PHP ;)
Sure, but it's a bit uncool to keep the same stuff in two places - I'm
thinking of a translation support for an app I write which supports
both AJAX/template-based client rendering and a more basic,
server-rendered version.

Currently, I have the stuff in a PHP array which generates a JSON file
with the translation upon manual rebuild. Alone the "support trailing
comma" function (to ease working with version control) would give me
the option of doing *everything* in JSON without manual rebuilds etc.

Marco