Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:83757
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain lsces.co.uk from 217.147.176.214 cause and error)
Message-ID: <54ED9E12.80808@lsces.co.uk>
Date: Wed, 25 Feb 2015 10:04:02 +0000
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
MIME-Version: 1.0
To: internals@lists.php.net
References: <CAEbg-4aR14ispgwzBmYxC1oFWPpKgdXTTmVcwJs_vRESKSw81A@mail.gmail.com> <CAGa2bXa7z=8SSTW=EnsccrzgJhVB9Lvm-ayQLbUUu6MPUUZyYA@mail.gmail.com> <alpine.DEB.2.11.1502250936390.5941@whisky.home.derickrethans.nl>
In-Reply-To: <alpine.DEB.2.11.1502250936390.5941@whisky.home.derickrethans.nl>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] [Discussion] Last chance for case-sensitive engine
From: lester@lsces.co.uk (Lester Caine)

On 25/02/15 09:40, Derick Rethans wrote:
> To be really honest, I don't think all of the pro's hold up. For a hash 
> check, there is no change really - the only change that is to remove the 
> zend_tolower. Previous discussions have IIRC shown that the performance 
> benefit is minimal. Compatibility with PSR's is also a moot point, as 
> there are just recommendations.

There is still the matter of 'internationalization', which is
technically a different RFC, but zend_tolower is only handling ASCII
character set? So modifying that function where appropriate may be
advantageous later.

> However, there are a few extra cons: You are going to break 
> people's code on a large scale. I simply don't think it is worth it 
> (again, just like when this discussion popped up every year or so for 
> the last decade).

Having been stung by the 'cons' already in reverse when moving perfectly
stable code from windows to linux I'd actually say that it would have
been a 'pro' if the mixed case stuff that previous programmers had used
had been eliminated. I take a lot more care now ensuring that case IS
consistent and if PHP nannied this in the same way it nannies some other
style points, then I would put under the pro rather than con!

Some of the BC areas being discussed do seem 'why put us through that',
but unicode is still being pushed to the sidelines and this is one of
those BC breaks which would help pave the way for a clean unicode core
in the future.

-- 
Lester Caine - G8HFL
-----------------------------
Contact - http://lsces.co.uk/wiki/?page=contact
L.S.Caine Electronic Services - http://lsces.co.uk
EnquirySolve - http://enquirysolve.com/
Model Engineers Digital Workshop - http://medw.co.uk
Rainbow Digital Media - http://rainbowdigitalmedia.co.uk