Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:79875
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.212.180 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <000c01d01ca0$7e70c850$7b5258f0$@yahoo.fr>
References: <000c01d01ca0$7e70c850$7b5258f0$@yahoo.fr>
Date: Tue, 23 Dec 2014 02:17:29 +0100
Message-ID: <CAH-PCH4gyTXFFYZ=-UR2KJ2y3PHzX32zqSbmwNHRqAQrC4CxaA@mail.gmail.com>
To: nf.laupretre@yahoo.fr
Cc: PHP Internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=f46d044267fe4dfba1050ad7f0b9
Subject: Re: [PHP-DEV] Proposal for PHP 7 : case-sensitive symbols
From: tyra3l@gmail.com (Ferenc Kovacs)

--f46d044267fe4dfba1050ad7f0b9
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Sat, Dec 20, 2014 at 11:01 PM, 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 think that the cost of that BC break is too high, and will only happen in
an alternative implementation (if at all).
Putting that aside, if we want to go down that road, we should first
discourage people from such usage, and as we never did that(no E_STRICT no
E_DEPRECATED) it would be extremely rude to remove support for that in 7.0.
I think that a Pull Request for adding E_STRICT or maybe even E_DEPRECATED
would have a chance of getting voted in but depends on the implementation
and how much overhead would it cost.

--=20
Ferenc Kov=C3=A1cs
@Tyr43l - http://tyrael.hu

--f46d044267fe4dfba1050ad7f0b9--