Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:100605
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.83.44 as permitted sender)
To: Nikita Popov <nikita.ppv@gmail.com>,
 "Christoph M. Becker" <cmbecker69@gmx.de>
Cc: "internals@lists.php.net" <internals@lists.php.net>
References: <c7746903-2e3a-3e86-59c9-63483b244feb@gmx.de>
 <CAF+90c_J3d4ws18e+JnMbFj_a4Co5s=wjfBR==CHD3Y8Dc9jkA@mail.gmail.com>
Message-ID: <752eaf1d-5603-70f5-8e69-b8243547cad1@gmail.com>
Date: Thu, 14 Sep 2017 14:22:34 -0700
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0)
 Gecko/20100101 Thunderbird/52.3.0
MIME-Version: 1.0
In-Reply-To: <CAF+90c_J3d4ws18e+JnMbFj_a4Co5s=wjfBR==CHD3Y8Dc9jkA@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Deprecate and remove case-insensitive constants?
From: smalyshev@gmail.com (Stanislav Malyshev)

Hi!

> +1 on doing this. I can understand having case-insensitive constants, but
> having both case-sensitive and case-insensitive at the same time is weird
> and rather useless. I imagine the only reason why this "feature" exists in
> the first place is to support arbitrary casing for true/false/null, which
> is better handled by special-casing these particular constants (something
> we already do for various other reasons). This will simplify the language

If we support all case-insensitive constants that are predefined (not
sure if any exts do that but we have to support those too if they do)
then I don't see a big problem in phasing-out user-defined ones.

After a quick gihub scan, I see there's some usage of case-insensitive
constants but most of it doesn't seem to be actually using that thing
(i.e. usages are in the same case as definition).

-- 
Stas Malyshev
smalyshev@gmail.com