Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:71690
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain ajf.me designates 198.187.29.241 as permitted sender)
Message-ID: <52E7F55F.7090801@ajf.me>
Date: Tue, 28 Jan 2014 18:22:23 +0000
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: Pierre Joye <pierre.php@gmail.com>
CC: PHP internals <internals@lists.php.net>
References: <CAEZPtU6749gD2a9BDzdTQoBPUsPDSspjukZvFw9qwt=Le5Q1zQ@mail.gmail.com>	<52E7D67D.1030308@ajf.me> <CAEZPtU6M3_x7Kv1U8gOAx3L3ZDZxt6UiV8RLxaY3voYUvnoqFw@mail.gmail.com>
In-Reply-To: <CAEZPtU6M3_x7Kv1U8gOAx3L3ZDZxt6UiV8RLxaY3voYUvnoqFw@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] some thoughts about php 6
From: ajf@ajf.me (Andrea Faulds)



On 28/01/14 16:13, Pierre Joye wrote:
> Anyone not being a developer will never use it. Let alone conservative
> projects, or already released applications. There is no gain. However
> there are tools already to apply whatever CS one wishes to existing
> source code, or to check CS on commit. That's what one can uses case
> sensitive naming without us having to break everything out there. I
> think we can disagree on that and do not discuss that forever, if
> there is a RFC about it, we will vote on it and that's it :) My
> mistake was to send this mail too early, more important points coming
> :)

I don't care about coding style. I care about sanity here, and I think 
case-insensitivity leads to more problems than it solves, especially, as 
others have pointed out, when autoloading comes into play.

A case-fixing tool could be run once on existing codebases, break no 
backwards compatibility, and make those codebases work on PHP 6.

-- 
Andrea Faulds
http://ajf.me/