Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:79831
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.223.173 as permitted sender)
MIME-Version: 1.0
Sender: yohgaki@gmail.com
In-Reply-To: <000c01d01ca0$7e70c850$7b5258f0$@yahoo.fr>
References: <000c01d01ca0$7e70c850$7b5258f0$@yahoo.fr>
Date: Sun, 21 Dec 2014 09:19:55 +0900
Message-ID: <CAGa2bXbWM+pJNWkzyy=8vtVvAhQ5Hv4BgLr2cRkvq0iFGdV9rA@mail.gmail.com>
To: nf.laupretre@yahoo.fr
Cc: "internals@lists.php.net" <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=001a113fd6463c3b26050aaee967
Subject: Re: [PHP-DEV] Proposal for PHP 7 : case-sensitive symbols
From: yohgaki@ohgaki.net (Yasuo Ohgaki)

--001a113fd6463c3b26050aaee967
Content-Type: text/plain; charset=UTF-8

Hi all,

On Sun, Dec 21, 2014 at 7:01 AM, F & N Laupretre <nf.laupretre@yahoo.fr>
wrote:

> 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.
>

Defining

thisismyfunction() {}

then call it

THISisMYFunction()

is not recommended at all. Keeping not recommended spec forever is not
a good idea. IMHO. Using strtolower() all over place in the Engine to keep
running not recommended code does not make much sense.

It's BC, but it would be easy spot it by an compatibility check script. Once
case is used properly, scripts run both new and old PHP. Therefore,
BC issue is not critical.

Regards,

--
Yasuo Ohgaki
yohgaki@ohgaki.net

--001a113fd6463c3b26050aaee967--