Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:60261
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain m.gmane.org designates 80.91.229.3 as permitted sender)
To: internals@lists.php.net
Date: Mon, 23 Apr 2012 13:22:23 +0300
Lines: 51
Message-ID: <jn3aht$tr6$1@dough.gmane.org>
References: <jmrdbg$bh4$1@dough.gmane.org> <CA+Ky_uM+m3pvDguD5+ihnJiz_FTmQd2LwdkdY_WjWDaJnyPBzw@mail.gmail.com> <jn0go8$sam$1@dough.gmane.org> <CA+Ky_uOUc66zGCoMiGigtWeNF=MpF_upTyGYhaCv-P08Y-toNg@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
User-Agent: Mozilla/5.0 (Windows NT 6.0; rv:11.0) Gecko/20120312 Thunderbird/11.0
In-Reply-To: <CA+Ky_uOUc66zGCoMiGigtWeNF=MpF_upTyGYhaCv-P08Y-toNg@mail.gmail.com>
Subject: Re: [PHP-DEV] Complete case-sensitivity in PHP
From: can5koy@gmail.com ("C.Koy")

On 4/22/2012 11:32 PM, Galen Wright-Watson wrote:
> 2012/4/22 C.Koy<can5koy@gmail.com>
>
>> On 4/21/2012 4:37 AM, Galen Wright-Watson wrote:
>
>> But, I did not start this thread to discuss such bug fix, because:
>>
>> 1. It does not take a genius to figure it out, and should take minutes to
>> implement for someone experienced in the internals. Given the 10 year span
>> and dozens of comments/complaints on the bug's entry, it's hard to say this
>> issue went unnoticed. So I had to conclude that such fix has quietly been
>> overruled for performance and/or other undisclosed reasons.
>>
>
> Why does it matter if a solution is simple?

It doesn't matter, you've misunderstood.
On the contrary, common sense dictates a simple solution should be 
applied (considering how deep in the PHP stack we're talking about).
And that's what makes me curious and confused about why this bug still 
exists. See, I'm drawing a conclusion with what little information I 
have, and stating the reasonings it's based on (first two statements).
Overall, that and the item following it were an explanation of "why I'm 
suggesting a major feature change in solution to a specific bug", 
although noone directly asked me to.

>
> If it's already been rejected privately, it's time to bring the reasons
> into the open (which is why I asked). If not, it should be considered
> publicly.

A comment dated 2002-09-26 on bug's page states the bug is fixed. The 
next comment dated 2006-02-17 states it reappeared.
I don't know who did what 10, 6 years ago but it's been revoked. Why?
That was the main reason I deemed this bug not fixable, hence suggest 
other ways to resolve.

>>
>> The abstract property that makes a locale problematic is obvious. I was
> looking for specific locales, as they need to be identified for a complete
> solution.
>

I'm not locale expert. Given the public complaints/bugs we can, in 
practice, assume this affects Turkish and Azerbaijani only. (I don't 
know about Kurdish)

best regards,