Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:85531
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.223.169 as permitted sender)
MIME-Version: 1.0
Sender: jakub.php@gmail.com
Date: Sun, 29 Mar 2015 20:33:21 +0100
Message-ID: <CAEKnhAHjM2RY+Z2iB7D5wAb=FA43vMkKb1+34O-rTsuV222YUg@mail.gmail.com>
To: PHP internals list <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=001a113f1c58359f2a05127270f2
Subject: JSON float number as string
From: bukka@php.net (Jakub Zelenka)

--001a113f1c58359f2a05127270f2
Content-Type: text/plain; charset=UTF-8

Hi,

I would like to add a new option to JSON for dealing with large floats. The
use case is mainly for decoder but can be used for encoder as well.

JSON_FLOAT_AS_STRING
decode: all float values will be decoded as string
- It's often an issue for very large float values with many fractional
digits that are coming from platforms that support larger float
representation than double. In that case the conversion is lost and there
is no way how to get it back (see http://bugs.php.net/68456 [pls ignore my
initial dump comments when I didn't get the issue :)] and an example of the
lost precision here http://3v4l.org/80iCh ). Converting the value to string
keep the precision and resolves the problem.

encode: all float values will be encoded as string
- re-using the constant for encoder makes sense if PHP creates JSON for
platform that support lower float type (e.g. C float) and the precision
loss is not acceptable


I think that this is more a bugfix as the precision is lost without any way
how to get it back (except pre-processing json string with regular
expression). I would like to add it to 5.6.x if there are no objections?

Cheers

Jakub

--001a113f1c58359f2a05127270f2--