Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:48213
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain pooteeweet.org from 188.40.37.16 cause and error)
Mime-Version: 1.0 (Apple Message framework v1078)
Content-Type: text/plain; charset=utf-8
In-Reply-To: <p2tcda548cc1005042344lf4b1fac4qb2318b28e219b1e1@mail.gmail.com>
Date: Wed, 5 May 2010 10:38:09 +0200
Cc: Adam Harvey <aharvey@php.net>,
 internals@lists.php.net
Content-Transfer-Encoding: quoted-printable
Message-ID: <E40DFD68-5B71-4646-9DCB-FA51A8026E64@pooteeweet.org>
References: <r2se50d0a481004182058i1ca96f6ka9f7a4e545c98e5e@mail.gmail.com> <p2ie50d0a481005040514h8720228qe2ae6a589deab4ab@mail.gmail.com> <p2tcda548cc1005042344lf4b1fac4qb2318b28e219b1e1@mail.gmail.com>
To: Patrick ALLAERT <patrickallaert@php.net>
Subject: Re: [PHP-DEV] Re: Turkish/Azeri locale support
From: mls@pooteeweet.org (Lukas Kahwe Smith)


On 05.05.2010, at 08:44, Patrick ALLAERT wrote:

> 2010/5/4 Adam Harvey <aharvey@php.net>:
>> On 19 April 2010 11:58, Adam Harvey <aharvey@php.net> wrote:
>>> As at least some of you would already be aware, there's a
>>> long-standing issue with using PHP in a Turkish or Azeri locale,
>>> namely that case-insensitive lookups within the Zend engine (method
>>> names, for example) fail on lookups involving upper-case I =
characters,
>>> since lower-case I in those languages is =C4=B1 instead of i (note =
the lack
>>> of a dot).
>>=20
>> Well, I'm going to assume that people have had whatever say they were
>> going to. It seems that we have three options, so let's put it to a
>> vote.
>>=20
>> (To be completely clear, this is purely for trunk. This certainly
>> isn't a candidate for backporting to 5.3.)
>>=20
>> The options are:
>>=20
>> 1. Apply Tomas's patch to make case-insensitive lookups
>> locale-ignorant. Pros: fixes immediate problem. Cons: breaks BC for
>> case-insensitive function/method name lookups for high-bit characters
>> in single-byte encodings. (Not that we've ever advertised or
>> documented that.)
>>=20
>> 2. Make function/method names case-sensitive, per Stan's e-mail. =
Pros:
>> fixes problem; brings PHP into line with most other languages; extra
>> consistency with variables; possible performance improvement. Cons: =
BC
>> break from current documented behaviour.
>=20
> Once and for all: +1 for #2 (BTW that kind of BC will not be that hard =
to fix!)

we have had the topic of making PHP case sensitive before. I do not find =
the above reason all that compelling to make this change. However there =
are several other reasons that imho are more relevant for making this =
change.

> RMs: should this really be part of PHP 5.4 if it gets approved?


no way.

regards,
Lukas Kahwe Smith
mls@pooteeweet.org