Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:90673 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 97829 invoked from network); 16 Jan 2016 01:40:54 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 16 Jan 2016 01:40:54 -0000 X-Host-Fingerprint: 90.212.141.145 unknown Received: from [90.212.141.145] ([90.212.141.145:12203] helo=localhost.localdomain) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id E0/00-32157-3AF99965 for ; Fri, 15 Jan 2016 20:40:51 -0500 Message-ID: To: internals@lists.php.net References: Date: Sat, 16 Jan 2016 01:40:46 +0000 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:42.0) Gecko/20100101 Firefox/42.0 SeaMonkey/2.39 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Posted-By: 90.212.141.145 Subject: Re: [RFC][VOTE] Number Format Separator From: ajf@ajf.me (Andrea Faulds) Hi Thomas, Thomas Punt wrote: > Hi internals! > > Voting has opened for the inclusion of a digit separator in PHP[1]. Voting ends in > one week's time on January 20th. > > Thanks, > Tom > > [1]: http://wiki.php.net/rfc/number_format_separator > Initially I was going to abstain from this vote, but I've changed my mind and I am now voting in favour of the RFC. When choosing whether to add features to the language, we must set a high standard, because every new additions means additional complexity and more knowledge PHP developers have to have. So, every new addition should be made to fit well with existing features, be useful, and This feature offers some benefit in some cases. It doesn't introduce much new complexity. There's no new syntax or tokens, it just modifies the form of the existing number tokens. It fits in well what's already there, consistently applying to all number literals. It follows established convention in other languages. Its appearance at least hints that values with these seperators are not constants or identifiers, but numbers, reducing potential for confusion. It limits its own application to prevent abuse (no leading, trailing, or repeated separators). And it's relatively intuitive. So I think it might be worth adding, thus my vote. Though we must be conservative with additions, this one doesn't seem to be too problematic. That said, I might be voting the wrong way. The feature does seem to have limited applicability. That's really the only thing I can say against it. Thanks. -- Andrea Faulds https://ajf.me/