Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:78643
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.192.44 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CA+sv8zB4TC_N_cZ6W_CkGZLXhFNTw23z-R197qEOT1v-VR4ksQ@mail.gmail.com>
References: <CA+sv8zB4TC_N_cZ6W_CkGZLXhFNTw23z-R197qEOT1v-VR4ksQ@mail.gmail.com>
Date: Tue, 4 Nov 2014 15:57:21 +0100
Message-ID: <CAH-PCH7=SZ710Pz5o80YSNRiAyRHivnoYt-A_OZbApDH7Jxc3Q@mail.gmail.com>
To: Juan Basso <jrbasso@gmail.com>, Jakub Zelenka <bukka@php.net>
Cc: PHP Internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=001a11c102642e75e4050709ae26
Subject: Re: [PHP-DEV] Add a new flag for json_encode
From: tyra3l@gmail.com (Ferenc Kovacs)

--001a11c102642e75e4050709ae26
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Tue, Nov 4, 2014 at 4:13 AM, Juan Basso <jrbasso@gmail.com> wrote:

> Hi,
>
> I opened a pull request[1] in order to solve the bug 50224[2] and it ende=
d
> creating this pull request to add a new flag called
> JSON_PRESERVE_FRACTIONAL_PART on json_encode function. This flag will mak=
e
> the json encode to output float number always with decimal part, even whe=
n
> it is 0.
>
> Currently if you try to convert 10.0 using json_encode it outputs 10. It
> means if you decode it it will give an integer instead a float. In PHP
> words, json_decode(json_encode(10.0)) !=3D=3D 10.0.
>
> After some researches and discussions it is not considered a bug because
> JSON specs treat integer and floats as number. Looking how other language=
s
> treat this encoding I could find it:
> - C (using lib jansson) and Ruby the output contains the decimal portion;
> - Python and Javascript outputs without the decimal portion.
>
> So it is kind of common to have different behaviors since JSON specs defi=
ne
> it as just number. The idea of the new flag is allow PHP to behave the bo=
th
> ways.
>
> In the pull request Stanislav Malyshev suggested to merge it in the 5.6,
> but just want to see if someone else has any objection. Ferenc Kovacs
> and Jakub Zelenka also are in favor of merging on 5.6.
> Jakub completed suggesting to have this option enabled by default on PHP =
7.
>
> Anyone has any objection on merging it on 5.6? Some comments about enabli=
ng
> it by default in 7?
>
> As a side note, with the pull request the encode of floats are about 20%
> faster, even after the flag check. This improvement just affect float
> encoding and has no impact on the other types.
>
> [1] https://github.com/php/php-src/pull/642
> [2] https://bugs.php.net/bug.php?id=3D50224
>
>
> Thanks,
> Juan Basso
>

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
Ferenc Kov=C3=A1cs
@Tyr43l - http://tyrael.hu

--001a11c102642e75e4050709ae26--