Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:88390 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 42273 invoked from network); 21 Sep 2015 19:35:18 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 21 Sep 2015 19:35:18 -0000 Authentication-Results: pb1.pair.com smtp.mail=anatol.php@belski.net; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=anatol.php@belski.net; sender-id=unknown Received-SPF: error (pb1.pair.com: domain belski.net from 85.214.73.107 cause and error) X-PHP-List-Original-Sender: anatol.php@belski.net X-Host-Fingerprint: 85.214.73.107 klapt.com Received: from [85.214.73.107] ([85.214.73.107:36855] helo=h1123647.serverkompetenz.net) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id D9/30-36219-3FB50065 for ; Mon, 21 Sep 2015 15:35:15 -0400 Received: by h1123647.serverkompetenz.net (Postfix, from userid 1006) id 4C1396D2004; Mon, 21 Sep 2015 21:35:12 +0200 (CEST) Received: from w530phpdev (p579F30E5.dip0.t-ipconnect.de [87.159.48.229]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by h1123647.serverkompetenz.net (Postfix) with ESMTPSA id C37E06D2002; Mon, 21 Sep 2015 21:35:08 +0200 (CEST) To: "'Yasuo Ohgaki'" , "'Kalle Sommer Nielsen'" Cc: "'Ferenc Kovacs'" , References: In-Reply-To: Date: Mon, 21 Sep 2015 21:35:06 +0200 Message-ID: <023701d0f4a4$a0da4f60$e28eee20$@belski.net> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable X-Mailer: Microsoft Outlook 15.0 Thread-Index: AQIuTDCwWc2HF4xophrruCZqRmQ9xAK8kBvIAb/EVTQDP8Pfqp1Oyf9A Content-Language: en-us Subject: RE: [PHP-DEV] Re: [RFC] [DISCUSSION] More precise float value From: anatol.php@belski.net ("Anatol Belski") Hi Yasuo, > -----Original Message----- > From: yohgaki@gmail.com [mailto:yohgaki@gmail.com] On Behalf Of Yasuo > Ohgaki > Sent: Sunday, September 20, 2015 11:49 PM > To: Kalle Sommer Nielsen > Cc: Anatoliy Belsky ; Ferenc Kovacs ; > internals@lists.php.net > Subject: Re: [PHP-DEV] Re: [RFC] [DISCUSSION] More precise float value >=20 > Hi Anatol and Ferenc, >=20 > On Sat, Sep 19, 2015 at 7:15 AM, Kalle Sommer Nielsen = wrote: > > I'm sorry I have not caught this any earlier, but even without > > consulting with Anatol, I'm not keen on adding this into 7.0, we are > > in RC stage, and I want us to focus on a stable release instead of > > adding more potential issues, I suggest you target 7.1 instead in = the > > RFC. > > > > (Ferenc and Anatol cc'd) >=20 > I was expecting this kind of reply for this RFC. > What do you think? >=20 > This RFC contains JSON float value precision change for PHP 5.6 so = that PHP > would not loose floating number information, as well as more precise = float > handling option for PHP 7.0. >=20 > FYI, var_dump()'s float precision was changed to use = serialize_precision as bug > fix before. >=20 Thanks for the ping. IMHO this is the stuff for 7.1. I actually saw the = discussions previously, but was rather thinking you was targeting 7.1 as = that was already the time of the feature freeze. Please keep in mind that we effectively have two RCs to do the remaining = stabilizations. And we probably should as much as possible. Because this = patch it's rather an enhancement to the current functionality which is = not indeed broken - I wouldn't see it as critical for 7.0. It should be = voted (and discussed if necessary) for 7.1, so we don't loop away from = our current situation. BTW I also had a comment there in the PR about = https://github.com/php/php-src/pull/1455/files#diff-c84859666ff690a113d55= ef1899d8bf4R149 - so if mode 0 ignores ndigits, why set it to 17 (or = anything else). Seems like an unnecessary action, but snprintf is used = quite frequently. But just as a notice on the side. Regards Anatol