Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:102722
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain kelunik.com from 85.215.255.50 cause and error)
MIME-Version: 1.0
References: <CAF+90c-WhpsCJQ9rB7vdqLv_10fjz-Eng=CHY2fk6W+eWGnVjA@mail.gmail.com>
 <9D.67.49043.CEA834B5@pb1.pair.com>
In-Reply-To: <9D.67.49043.CEA834B5@pb1.pair.com>
Date: Tue, 10 Jul 2018 19:18:05 +0200
Message-ID: <CANUQDCjg22wdi+Y-dPHCOGgEsX9nkkEmN_xx=ApnLv9o+r6RoQ@mail.gmail.com>
To: Andrea Faulds <ajf@ajf.me>
Cc: PHP Internals <internals@lists.php.net>
Content-Type: text/plain; charset="UTF-8"
Subject: Re: [PHP-DEV] Re: [VOTE] Deprecate and remove case-insensitive constants
From: me@kelunik.com (Niklas Keller)

> 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.

No, thanks. The fallback is already a bad thing for functions, we
don't need another one.

If such a feature would be implemented, it'd probably be via combined
symbol tables, making either everything case-insensitive or everything
case-sensitive.

Regards, Niklas