Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:71691
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.217.169 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <52E7F55F.7090801@ajf.me>
References: <CAEZPtU6749gD2a9BDzdTQoBPUsPDSspjukZvFw9qwt=Le5Q1zQ@mail.gmail.com>
	<52E7D67D.1030308@ajf.me>
	<CAEZPtU6M3_x7Kv1U8gOAx3L3ZDZxt6UiV8RLxaY3voYUvnoqFw@mail.gmail.com>
	<52E7F55F.7090801@ajf.me>
Date: Tue, 28 Jan 2014 19:31:26 +0100
Message-ID: <CAEZPtU6s07t2+vE8S3FhDAiXhfstdhk+=8PE0XOos-2aQsuvHw@mail.gmail.com>
To: Andrea Faulds <ajf@ajf.me>
Cc: PHP internals <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Subject: Re: [PHP-DEV] some thoughts about php 6
From: pierre.php@gmail.com (Pierre Joye)

On Tue, Jan 28, 2014 at 7:22 PM, Andrea Faulds <ajf@ajf.me> wrote:
>
>
> 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.

Coding standards are part of the problem, that's not something we can ignore.

>  I care about sanity here,

Why pre commit checks do add sanity checks to existing projects, today.

> and I think
> case-insensitivity leads to more problems than it solves, especially, as
> others have pointed out, when autoloading comes into play.


Right, while I did not meet one for years but we may work with
different projects or developers.


> A case-fixing tool could be run once on existing codebases, break no
> backwards compatibility, and make those codebases work on PHP 6.


I will 200% surely change my mind the day I see such tool working with
all major frameworks and applications out there without a single point
of failure.

However, I would suggest to waste too much time arguing about case
sensitivity, almost all of us agree that it is a good thing to have.
Only question is if it is a good idea at all to do it and only the
votes will solve this question.

Cheers,
-- 
Pierre

@pierrejoye | http://www.libgd.org