Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:73135 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 6444 invoked from network); 13 Mar 2014 22:52:29 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 13 Mar 2014 22:52:29 -0000 Authentication-Results: pb1.pair.com header.from=ajf@ajf.me; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=ajf@ajf.me; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain ajf.me designates 198.187.29.241 as permitted sender) X-PHP-List-Original-Sender: ajf@ajf.me X-Host-Fingerprint: 198.187.29.241 imap3-1.ox.registrar-servers.com Received: from [198.187.29.241] ([198.187.29.241:35790] helo=imap3-1.ox.registrar-servers.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id CC/FA-47923-AA632235 for ; Thu, 13 Mar 2014 17:52:28 -0500 Received: from localhost (localhost [127.0.0.1]) by oxmail.registrar-servers.com (Postfix) with ESMTP id 152C32A0084; Thu, 13 Mar 2014 18:52:24 -0400 (EDT) X-Virus-Scanned: Debian amavisd-new at imap3.ox.registrar-servers.com Received: from oxmail.registrar-servers.com ([127.0.0.1]) by localhost (imap3.ox.registrar-servers.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 8E9hIPZMPJm0; Thu, 13 Mar 2014 18:52:23 -0400 (EDT) Received: from [192.168.0.8] (unknown [90.203.28.187]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by oxmail.registrar-servers.com (Postfix) with ESMTPSA id 6D6BA2A0083; Thu, 13 Mar 2014 18:52:21 -0400 (EDT) Content-Type: multipart/alternative; boundary="Apple-Mail=_46677F32-246B-4260-BA4B-2081937A5354" Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\)) In-Reply-To: Date: Thu, 13 Mar 2014 22:52:19 +0000 Cc: Jakub Zelenka , PHP internals list Message-ID: <8C0E8F2C-4264-4B19-A9DD-67302A39F4CC@ajf.me> References: To: Marco Schuster X-Mailer: Apple Mail (2.1874) Subject: Re: [PHP-DEV] New JSON parser From: ajf@ajf.me (Andrea Faulds) --Apple-Mail=_46677F32-246B-4260-BA4B-2081937A5354 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=windows-1252 On 13 Mar 2014, at 22:37, Marco Schuster 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. >=20 > 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=92s great strengths is that there is only a = single, canonical JSON standard. Implementing other standards would be = damaging to interoperability. If people want nice config files, they can use PHP ;) -- Andrea Faulds http://ajf.me/ --Apple-Mail=_46677F32-246B-4260-BA4B-2081937A5354--