Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:102671 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 9744 invoked from network); 9 Jul 2018 16:18:54 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 9 Jul 2018 16:18:54 -0000 X-Host-Fingerprint: 85.230.241.5 c-05f1e655.79-4-64736c10.bbcust.telenor.se Received: from [85.230.241.5] ([85.230.241.5:22261] helo=localhost.localdomain) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 9D/67-49043-CEA834B5 for ; Mon, 09 Jul 2018 12:18:52 -0400 Message-ID: <9D.67.49043.CEA834B5@pb1.pair.com> To: internals@lists.php.net References: Date: Mon, 9 Jul 2018 18:18:48 +0200 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:49.0) Gecko/20100101 Firefox/49.0 SeaMonkey/2.46 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Posted-By: 85.230.241.5 Subject: Re: [VOTE] Deprecate and remove case-insensitive constants From: ajf@ajf.me (Andrea Faulds) Hi Nikita, I'm a terrible person for only bringing this up now (I apologise for not following the list as closely as I used to), but one reason case-insensitive constants are maybe useful is they leave open the possibility of being able to access functions as values in future: like some constants, function names are case-insensitive, and a fallback could be added to constant accesses to return a closure of the function with the same name if no constant is found. Of course, removing case-insensitive constants wouldn't preclude such a feature, just make it a little more annoying to implement, so this is not really a significant reason to vote against. To that end, I'll vote in favour of this deprecation. Thanks! -- Andrea Faulds https://ajf.me/