Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:90555 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 90376 invoked from network); 12 Jan 2016 15:11:05 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 12 Jan 2016 15:11:05 -0000 Authentication-Results: pb1.pair.com smtp.mail=tpunt@hotmail.co.uk; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=tpunt@hotmail.co.uk; sender-id=pass Received-SPF: pass (pb1.pair.com: domain hotmail.co.uk designates 157.55.2.84 as permitted sender) X-PHP-List-Original-Sender: tpunt@hotmail.co.uk X-Host-Fingerprint: 157.55.2.84 dub004-omc4s9.hotmail.com Received: from [157.55.2.84] ([157.55.2.84:58366] helo=DUB004-OMC4S9.hotmail.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 60/2A-32047-78715965 for ; Tue, 12 Jan 2016 10:11:05 -0500 Received: from DUB129-W51 ([157.55.2.73]) by DUB004-OMC4S9.hotmail.com over TLS secured channel with Microsoft SMTPSVC(7.5.7601.23008); Tue, 12 Jan 2016 07:11:01 -0800 X-TMN: [vmeMZ+eXktFGwMi0rf2IIK9dzV6reL/I] X-Originating-Email: [tpunt@hotmail.co.uk] Message-ID: To: Christoph Becker , "internals@lists.php.net" Date: Tue, 12 Jan 2016 15:11:01 +0000 Importance: Normal In-Reply-To: <5695044F.1070509@gmx.de> References: ,,<5695044F.1070509@gmx.de> Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginalArrivalTime: 12 Jan 2016 15:11:01.0403 (UTC) FILETIME=[72C7AEB0:01D14D4B] Subject: RE: [PHP-DEV] [RFC] Number Format Separator From: tpunt@hotmail.co.uk (Thomas Punt) Hi=A0Christoph=2C=0A= =0A= > echo 1_000=3B=0A= > will print=0A= > 1000=0A= >=0A= > I think it is important to explicitly note that in the RFC.=0A= >=0A= > With regard to "stringy numerics": besides the potential BC break=2C IMHO= =0A= > there is no need to support digit separators for string literals at all= =2C=0A= > because that could easily be provided by a userland function. Maybe=0A= > it's worth pointing that out in the RFC.=0A= =0A= Thanks for the comments - I've update the RFC accordingly.=0A= =0A= -Tom =