Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:78658
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: <CAEKnhAFrSd0dMMER6rYpw2Y-SS4wMF1SLS83C-44RdiYdg+HHg@mail.gmail.com>
Date: Tue, 4 Nov 2014 18:14:13 +0000
Cc: Ferenc Kovacs <tyra3l@gmail.com>,
 Juan Basso <jrbasso@gmail.com>,
 PHP Internals <internals@lists.php.net>
Content-Transfer-Encoding: quoted-printable
Message-ID: <76457381-6DBD-4C20-B18F-7CFB9D2EC55A@ajf.me>
References: <CA+sv8zB4TC_N_cZ6W_CkGZLXhFNTw23z-R197qEOT1v-VR4ksQ@mail.gmail.com> <CAH-PCH7=SZ710Pz5o80YSNRiAyRHivnoYt-A_OZbApDH7Jxc3Q@mail.gmail.com> <CAEKnhAFrSd0dMMER6rYpw2Y-SS4wMF1SLS83C-44RdiYdg+HHg@mail.gmail.com>
To: Jakub Zelenka <bukka@php.net>
Subject: Re: [PHP-DEV] Add a new flag for json_encode
From: ajf@ajf.me (Andrea Faulds)


> On 4 Nov 2014, at 17:07, Jakub Zelenka <bukka@php.net> wrote:
>=20
> I would really like to see it as default in the next major as it is a
> useful feature.
>=20
> However I don't like adding new flag. The reason for that is that it
> becomes useless after 7 is realesed. It would be useful only for =
>5.6.3 and
> <7.0 though. The only use case in PHP 7 would be just to disable the =
flag
> but that won't be very nice and completely different than other json
> constant usage It means doing something like $options &
> ~JSON_PRESERVE_FRACTIONAL_PART ... It's a bit messy IMHO. Think that =
it
> would be much better to wait till 7 with this feature.

I really don=E2=80=99t like the idea of making this the default. On =
32-bit systems, floats give you, effectively, extra integer range up =
until you hit 2^52, and indeed all JS integer values are just floats =
within that range. I don=E2=80=99t think they should be represented as =
floats. It=E2=80=99d go weirdly with 64-bit PHP, which can decode such =
values to integers, which would then not handle the range beyond 2^52 =
nicely.

Also, it wouldn=E2=80=99t go well for cross-version compatibility with =
my bigint RFC here.

--
Andrea Faulds
http://ajf.me/