Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:79939
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.42 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <009a01d01ff4$7d145470$773cfd50$@tekwire.net>
References: <000c01d01ca0$7e70c850$7b5258f0$@yahoo.fr>
	<CAH-PCH4gyTXFFYZ=-UR2KJ2y3PHzX32zqSbmwNHRqAQrC4CxaA@mail.gmail.com>
	<CAEZPtU6HhhNip_OYFAhc2LDvbZ_DZaZHTzoNTgTCR=qQbNRm+w@mail.gmail.com>
	<000d01d01ec2$46f2f280$d4d8d780$@yahoo.fr>
	<009a01d01ff4$7d145470$773cfd50$@tekwire.net>
Date: Thu, 25 Dec 2014 13:08:17 +0100
Message-ID: <CAF+90c9LZFx47e5Af=45v0wxK2iyLPnarVZRHgAmOqvPzLG8RQ@mail.gmail.com>
To: francois@tekwire.net
Cc: Pierre Joye <pierre.php@gmail.com>, Ferenc Kovacs <tyra3l@gmail.com>, 
	Guilherme Blanco <guilhermeblanco@gmail.com>, Alain Williams <addw@phcomp.co.uk>, 
	David Muir <davidkmuir@gmail.com>, Yasuo Ohgaki <yohgaki@ohgaki.net>, 
	Xinchen Hui <laruence@php.net>, Mike Dugan <mike@mjdugan.com>, Andrea Faulds <ajf@ajf.me>, 
	Kevin Israel <pleasestand@live.com>, PHP Internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=f46d043be12c6ea34b050b09435a
Subject: Re: [PHP-DEV] Proposal for PHP 7 : case-sensitive symbols
From: nikita.ppv@gmail.com (Nikita Popov)

--f46d043be12c6ea34b050b09435a
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Thu, Dec 25, 2014 at 4:40 AM, Fran=C3=A7ois Laupretre <francois@tekwire.=
net>
wrote:

> > > De : Pierre Joye [mailto:pierre.php@gmail.com]
> >
> > > Anyone dying while waiting to see PHP having case sensitive symbols
> > > handling should go ahead with a RFC.
>
> For those interested, I just created a PR to raise an E_STRICT message on
> class and function/method case mismatch :
>
> https://github.com/php/php-src/pull/965
>
> It is not complete yet,  as some cases are not trapped, especially for
> functions, and the corresponding tests are missing. I'll try to write the
> RFC (to propose the feature for PHP7) and finish the patch this week.
> Checking constants is more complex than expected as the namespace part is
> converted to lowercase during the compile phase. This RFC will deal with
> classes and functions (including class methods) only.
>

May I recommend to only target class and class-like names for an initial
RFC? Those have the strongest argument in favor of case-sensitivity given
how current autoloader implementations work - essentially the
case-insensitivity doesn't properly work anyway in modern code.

Constants in particular are more problematic, because they are currently
only partially case-sensitive and there are some constants (namely true,
false and null) where case sensitivity must not be enforced. So if you want
to make constants fully case sensitive those three would have to become
reserved keywords.

So, I think this has more chances if you tackle one issue at a time. I'd
also appreciate having a voting option for removing case-insensitivity
right away, as opposed to throwing E_STRICT/E_DEPRECATED. If we want to
change this, I personally would rather drop it right away than start
throwing E_STRICT warnings that would make the case-insensitive usage
impossible anyway.

Nikita

--f46d043be12c6ea34b050b09435a--