Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:78649
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain ajf.me designates 192.64.116.208 as permitted sender)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 8.0 \(1990.1\))
In-Reply-To: <CAH-PCH7=SZ710Pz5o80YSNRiAyRHivnoYt-A_OZbApDH7Jxc3Q@mail.gmail.com>
Date: Tue, 4 Nov 2014 16:35:34 +0000
Cc: Juan Basso <jrbasso@gmail.com>,
 Jakub Zelenka <bukka@php.net>,
 PHP Internals <internals@lists.php.net>
Content-Transfer-Encoding: quoted-printable
Message-ID: <869A4686-18BE-4A6E-8B1F-B4312DD27ED1@ajf.me>
References: <CA+sv8zB4TC_N_cZ6W_CkGZLXhFNTw23z-R197qEOT1v-VR4ksQ@mail.gmail.com> <CAH-PCH7=SZ710Pz5o80YSNRiAyRHivnoYt-A_OZbApDH7Jxc3Q@mail.gmail.com>
To: Ferenc Kovacs <tyra3l@gmail.com>
Subject: Re: [PHP-DEV] Add a new flag for json_encode
From: ajf@ajf.me (Andrea Faulds)


> On 4 Nov 2014, at 14:57, Ferenc Kovacs <tyra3l@gmail.com> wrote:
>=20
> Hi,
>=20
> 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.

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.

--
Andrea Faulds
http://ajf.me/