Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:79934
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.216.182 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 16:02:24 +1100
Message-ID: <CAEZPtU7NWHDqv72azTc0FrJO-359zQbWCke3LuzJaOdLqT7x5g@mail.gmail.com>
To: francois@tekwire.net
Cc: 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: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] Proposal for PHP 7 : case-sensitive symbols
From: pierre.php@gmail.com (Pierre Joye)

Hi Fran=C3=A7ois,

On Thu, Dec 25, 2014 at 2:40 PM, 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 fu=
nctions, 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.
>
>> He will also have to deal with
>> file ops while being at it. Should they remain case insensitive? Do
>> manual checks to match the path actually being requested (ie. possible
>> on windows using meta info), or keep everything the way it is now?
>
> Do you mean simulating case-sensitive paths on case-insensitive file syst=
ems ? Why not, depending on the overhead it brings. Unfortunately, I don't =
have the Windows skills required to work on the subject.
>
> About the overhead the check introduces, note that it is supposed to be t=
emporary. The final goal is to store symbols as-Is, eliminating the need fo=
r lowercase conversions. This would remove a lot of allocations and calls t=
o zend_str_tolower_copy(). This would also remove a lot of code.
>

Thanks for putting the RFC together. Let sort that out once and for all :)

I am definitively not in favor of case sensitivity. However it is
still a good thing to have that RFC as this topic keeps pop up once in
a while.

About the patch:

It has to take care about how userland codes (autoloader) will deal
with case insensitive file systems. Will they have to take care of it
themselves? Or will we keep them the way it is now? You can't simulate
case sensitive paths on case insensitive file systems. Some ops may
work, but PHP's IO have to be changed too if we do that, and this is
totally going too far for my taste :)

Cheers,
--=20
Pierre

@pierrejoye | http://www.libgd.org