Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:60247
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: unknown (pb1.pair.com: domain php.net does not designate 91.184.32.3 as permitted sender)
Message-ID: <4F91EE62.8080400@php.net>
Date: Sat, 21 Apr 2012 01:16:50 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:11.0) Gecko/20120329 Thunderbird/11.0.1
MIME-Version: 1.0
To: internals@lists.php.net
References: <jmrdbg$bh4$1@dough.gmane.org> <CAF+90c8NxUvXOEbFbN=U6QBNqvHLsa9Jfgx_1fpWss5ASCX11Q@mail.gmail.com> <CAL0xaBGfw35FPFTs=CZwc4OLDzB9N6N2uHdQsi8vmagmB-qVXA@mail.gmail.com> <CAL+t6cGM7gBWsiPYn8EbTEZm=OBb1=vrWzbyURRTgCvvKOUwLg@mail.gmail.com> <CAL+t6cECGQHJyxKew=U5t_wJV=8fKf6X-UaiwiEChy2=UE0=uw@mail.gmail.com> <CAGsnKxanO0oraHHB=+v61=-y7WtQR5vbN1fxHHzcagjFncmveg@mail.gmail.com> <CAL+t6cGksdaPJUanXxRcV25dNz2bPXd72SZJ-Yjs0M9ni28Nyw@mail.gmail.com> <CAKOpQSxbmcn2wxLuUMOpLd0NbNL==dV3cm4rhWmW_rNsjukNFw@mail.gmail.com> <jmsb3a$ulc$1@dough.gmane.org>
In-Reply-To: <jmsb3a$ulc$1@dough.gmane.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Complete case-sensitivity in PHP
From: neufeind@php.net (Stefan Neufeind)

On 04/20/2012 08:48 PM, C.Koy wrote:
> On 4/20/2012 8:57 PM, Kris Craig wrote:
>>
>> Turkish localization notwithstanding (I confess that I know absolutely *
>> nothing* about that lol), one possible use-case could be if you're
>> including an external library/framework that contains a function with the
>> same name but different case.  I'm not sure how likely that is, mind you,
>> but I can see that as one potential benefit.  Either way, I guess my
>> point
>> is that the arguments for/against this seem to parallel the arguments for
>> Windows-style fso case-insensitivity vs. Unix-style fso case-sensitivity.
> 
> Java, C#, Python, Ruby... are all case-sensitive. This is not a feature
> to be (mis-)used so that one can have a function named myfunc() and
> MyFunc() in the same code base.
> Case-insensitive class/function/interface names is a confusion for
> everyone with non-PHP development experience. There's not a modern OO
> platform that defines an interface named 'IDispatch' and later allows it
> to be referenced as 'idispatch' or 'iDispatch'. And PHP is becoming more
> OO with every major release.
> Overall, full case-sensitivity seems to be a natural step in PHP's
> evolution.

I also have the feeling that cleaner code with consistent case would be
a benefit. While I admit we can't change that from one day to the other
(as we couldn't with other changes) I think we might possibly add a
special kind of "deprecation" where the non-matching case would still
work but (if you activate those deprecation-warnings) would trigger
warnings so you can clean up your code.

Various projects that I work on take explicit care of the case when
auto-creating classnames etc. - not because they must but because they
want to be consistent. And that's the thing I like about it.


Regards,
 Stefan