Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:60249
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.210.170 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <jmrdbg$bh4$1@dough.gmane.org>
References: <jmrdbg$bh4$1@dough.gmane.org>
Date: Fri, 20 Apr 2012 18:37:42 -0700
Message-ID: <CA+Ky_uM+m3pvDguD5+ihnJiz_FTmQd2LwdkdY_WjWDaJnyPBzw@mail.gmail.com>
To: "C.Koy" <can5koy@gmail.com>
Cc: internals@lists.php.net
Content-Type: multipart/alternative; boundary=14dae9340d19e79ce604be267586
Subject: Re: [PHP-DEV] Complete case-sensitivity in PHP
From: ww.galen@gmail.com (Galen Wright-Watson)

--14dae9340d19e79ce604be267586
Content-Type: text/plain; charset=ISO-8859-9
Content-Transfer-Encoding: quoted-printable

On Fri, Apr 20, 2012 at 3:20 AM, C.Koy <can5koy@gmail.com> wrote:

>
> As the recent comments on that page indicate, there's not a deterministic
> way to resolve this issue, apart from eliminating tolower() calls for
> function/class names during lookup. Hence totally case-sensitive PHP.
>
>
What about instead creating a special-purpose Zend function to normalize
class names (zend_normalize_class_name, or zend_classname_tolower)? This
function would examine the current locale and, if it's a problematic one,
convert the string to lower case on its own (calling zend_tolower on
non-problematic characters). Alternatively, zend_normalize_class_name could
switch LC_CTYPE to an appropriate locale (e.g. "UTF-8"; the locale could be
determined at compile time), call zend_str_tolower_copy, then switch back
before returning. Then, any appropriate function (e.g.
zend_resolve_class_name, zend_lookup_class_ex, class_exists,  class_alias)
would call zend_normalize_class_name instead of zend_str_tolower_copy/
zend_str_tolower_dup.

The two problems with this approach are
1) additional time-cost. However, if done right, this should have little
impact.
2) break class names using words in the locale-language. For example, a
class named "IzgaraG=F6r=FCn=FCm=FC" would be converted to "izgarag=F6r=FCn=
=FCm=FC", rather
than "=FDzgarag=F6r=FCn=FCm=FC". However, this impact should be less than t=
hat caused
by the current bug.

Does this bug pop-up for locales other than Turkish, Azerbaijani and Kurdis=
h
?

--14dae9340d19e79ce604be267586--