Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:79840
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.216.46 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <000c01d01ca0$7e70c850$7b5258f0$@yahoo.fr>
References: <000c01d01ca0$7e70c850$7b5258f0$@yahoo.fr>
Date: Sun, 21 Dec 2014 16:20:13 +1100
Message-ID: <CAEZPtU5hnq9wGp=ZxJmn_Tqy0XLvA3WJMsyouEf32t-97jUjdQ@mail.gmail.com>
To: nf.laupretre@yahoo.fr
Cc: PHP internals <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Subject: Re: [PHP-DEV] Proposal for PHP 7 : case-sensitive symbols
From: pierre.php@gmail.com (Pierre Joye)

On Sun, Dec 21, 2014 at 9:01 AM, F & N Laupretre <nf.laupretre@yahoo.fr> wrote:
> Hi,
>
>
>
> I don't know if this was discussed before. So, tell me what you think before
> I write an RFC.
>
>
>
> I would like to propose that namespaces, functions, and classes become
> case-sensitive (constants are already case-sensitive). Actually, I never
> understood why they are case-insensitive. Even if the performance gain is
> negligible, I think it could be the right time to question this.

I have hard time to see the benefits of breaking so many codes for that.

Userland codes use to rely on case sensitivity naming, based on coding
standard. But for internals names, it is going to be a major pain.

Cheers,
Pierre