Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:100596
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: softfail (pb1.pair.com: domain golemon.com does not designate 209.85.216.170 as permitted sender)
MIME-Version: 1.0
Sender: php@golemon.com
In-Reply-To: <c7746903-2e3a-3e86-59c9-63483b244feb@gmx.de>
References: <c7746903-2e3a-3e86-59c9-63483b244feb@gmx.de>
Date: Thu, 14 Sep 2017 11:38:48 -0400
Message-ID: <CAESVnVpw9y4V8prSojbH1+HEf6OrT76FjOwaBvaq=bR9BGMJww@mail.gmail.com>
To: "Christoph M. Becker" <cmbecker69@gmx.de>
Cc: "internals@lists.php.net" <internals@lists.php.net>
Content-Type: text/plain; charset="UTF-8"
Subject: Re: [PHP-DEV] Deprecate and remove case-insensitive constants?
From: pollita@php.net (Sara Golemon)

On Tue, Sep 12, 2017 at 8:02 AM, Christoph M. Becker <cmbecker69@gmx.de> wrote:
> Usually constant identifiers are treated case-sensitive in PHP.  This is
> always the case for constants defined via a `const` declaration.
> However, define() allows to pass TRUE as third argument to define a
> case-insensitive constant.  This feature appears to potentially result
> in confusion, and also causes bugs as shown in
> <https://bugs.php.net/74450>.  See an example created by Nikita to see
> some probably unexpected behavior: <https://3v4l.org/L6nCp>.
>
I'd just like to ask everyone on this thread to circle back to the
actual topic: Case-Insensitive Constants.  Nothing else is on topic
here.  If you'd like to argue the value of Turkish case folding and
its impact on combined symbol tables in 40 year old software, I
encourage you to start a new thread for that topic.

Of the minority of responses to this thread reflecting on the actual
goal of the proposal, I've seen responses from "sure, why not?" to
"what's the point?", but if there was a coherent argument firmly
against, I must have missed it.

So could we focus on the topic at hand, please?

-Sara