Re: Deprecate and remove case-insensitive constants?
| From: | Christoph M. Becker | Date: | Tue, 12 Sep 2017 21:02:14 +0000 |
| Subject: | Re: Deprecate and remove case-insensitive constants? | ||
| References: | 1 2 3 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-100552@lists.php.net to get a copy of this message | ||
On 12.09.2017 at 21:55, Sara Golemon wrote:
> On Tue, Sep 12, 2017 at 7:43 PM, Stanislav Malyshev <smalyshev@gmail.com> wrote:
>
>> I'm worried about TRUE vs. True vs. true though - I've see all of those used
>> around the code (not tRuE though ;) and breaking that would add a ton of
>> meaningless work to maintainers without any upside. Same with NULL/null etc.
>
> We could always special case these in the lexer, or during
> compile-time constant folding. I agree they're a concern (and already
> noted as much in my previous reply), but they're an entirely tractable
> concern.
Sorry, I forgot to mention these special constants which are reserved
words right now. Of course, these have to stay case-insensitive, and we
simply could promote them to keywords which are case-insensitive, anyway.
--
Christoph M. Becker