Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:78657 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 81218 invoked from network); 4 Nov 2014 18:11:24 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 4 Nov 2014 18:11:24 -0000 Authentication-Results: pb1.pair.com smtp.mail=ajf@ajf.me; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=ajf@ajf.me; sender-id=pass Received-SPF: pass (pb1.pair.com: domain ajf.me designates 198.187.29.245 as permitted sender) X-PHP-List-Original-Sender: ajf@ajf.me X-Host-Fingerprint: 198.187.29.245 imap11-3.ox.privateemail.com Received: from [198.187.29.245] ([198.187.29.245:53085] helo=imap11-3.ox.privateemail.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 07/EC-06676-BC619545 for ; Tue, 04 Nov 2014 13:11:24 -0500 Received: from localhost (localhost [127.0.0.1]) by mail.privateemail.com (Postfix) with ESMTP id DC2EE8800EB; Tue, 4 Nov 2014 13:11:20 -0500 (EST) X-Virus-Scanned: Debian amavisd-new at imap11.ox.privateemail.com Received: from mail.privateemail.com ([127.0.0.1]) by localhost (imap11.ox.privateemail.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id MBtoIL2XRw76; Tue, 4 Nov 2014 13:11:20 -0500 (EST) Received: from oa-edu-170-172.wireless.abdn.ac.uk (oa-edu-170-172.wireless.abdn.ac.uk [137.50.170.172]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.privateemail.com (Postfix) with ESMTPSA id D1DFB8800F6; Tue, 4 Nov 2014 13:11:19 -0500 (EST) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 8.0 \(1990.1\)) In-Reply-To: Date: Tue, 4 Nov 2014 18:11:18 +0000 Cc: Juan Basso , Jakub Zelenka , PHP Internals Content-Transfer-Encoding: quoted-printable Message-ID: References: <869A4686-18BE-4A6E-8B1F-B4312DD27ED1@ajf.me> To: Ferenc Kovacs X-Mailer: Apple Mail (2.1990.1) Subject: Re: [PHP-DEV] Add a new flag for json_encode From: ajf@ajf.me (Andrea Faulds) > On 4 Nov 2014, at 16:41, Ferenc Kovacs wrote: >=20 >=20 >=20 > On Tue, Nov 4, 2014 at 5:35 PM, Andrea Faulds wrote: >=20 > > On 4 Nov 2014, at 14:57, Ferenc Kovacs wrote: > > > > Hi, > > > > just a slight correction: > > as far as I can tell, Jakus was ok with the general idea and even = with > > turning this into the default, but he stated that it should only = happen in > > a major version (as it would cause a slight BC, maybe this could = cause > > problems for some people who are expecting the zeroes to be = truncated from > > integer values) and he also stated that he thinks that there is no = reason > > for a hurry to have this in a micro release, so this could wait = until 7.0. >=20 > Why would this cause a BC break? If we=E2=80=99re just adding a new, = optional, off-by-default option, it shouldn=E2=80=99t break anything. >=20 > please re-read my previous mail: > "__turning this into the default__, but he stated that it __should = only happen in a major version__=E2=80=9D=20 Right, my bad. I read it as =E2=80=9CThis [including possibly turning = this into the default] should only happen in a major version=E2=80=9D, I = see what you meant. Sorry for the misunderstanding, in retrospect the = other interpretation would=E2=80=99ve made more sense. -- Andrea Faulds http://ajf.me/