Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:79854
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.220.43 as permitted sender)
References: <000c01d01ca0$7e70c850$7b5258f0$@yahoo.fr> <CAKxcST_MkPwZvBBKn-ya8SLVskZMwOhkHepxLeL8NbYNLU=cRw@mail.gmail.com> <BLU436-SMTP3673A56D45011DAE4484F7C1680@phx.gbl>
Mime-Version: 1.0 (1.0)
In-Reply-To: <BLU436-SMTP3673A56D45011DAE4484F7C1680@phx.gbl>
Content-Type: text/plain;
	charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Message-ID: <B5396DC0-FFE5-4DE0-B356-02E6097A3F8F@gmail.com>
Cc: Paul Dragoonis <dragoonis@gmail.com>,
 "nf.laupretre@yahoo.fr" <nf.laupretre@yahoo.fr>,
 PHP Internals List <internals@lists.php.net>
Date: Mon, 22 Dec 2014 10:33:03 +1100
To: Kevin Israel <pleasestand@live.com>
Subject: Re: [PHP-DEV] Proposal for PHP 7 : case-sensitive symbols
From: davidkmuir@gmail.com (David Muir)


> On 21 Dec 2014, at 10:32 am, Kevin Israel <pleasestand@live.com> wrote:
>=20
>> On 12/20/2014 05:16 PM, Paul Dragoonis wrote:
>> It's too big of a BC change firstly.
>>=20
>> Secondly it has no language benefit or developer benefit.
>=20
> Are you sure? Autoloading schemes such as PSR-4 derive pathnames from
> class names without converting them to lowercase. If case mismatches go
> undetected and unreported, a project might work on a developer's Windows
> desktop (case-insensitive) yet not when uploaded to a Linux web server
> (case-sensitive). Or when an object instantiation or a static method
> call using the correct case is removed from the code, a later call using
> the incorrect case might break.
>=20
> Backward compatibility is perhaps a good reason to not make this change.
> However, I would like to see at least an option to report case
> mismatches in class names as E_STRICT errors and possibly a way to
> disable that for specific files or classes when necessary.
>=20
>> On 20 Dec 2014 22:01, "F & N Laupretre" <nf.laupretre@yahoo.fr> wrote:
>=20
>>> 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 i=
s
>>> negligible, I think it could be the right time to question this.
>=20
> --=20
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>=20


+1 on E_STRICT warning for case mismatch on class names. Also +1 on eventual=
 case sensitivity for userland class names. Not convinced the rest is worth i=
t.

The insensitivity makes code brittle. Sometimes the same code will run fine,=
 and other times it breaks depending on what lines triggered the auto loader=
. If you instantiate a Foo instance first, then instantiate a new foo, the c=
ode runs fine, but if you try to instantiate a new foo first, we get a fatal=
 error.

Cheers,
David=