Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:83741 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 43887 invoked from network); 25 Feb 2015 05:37:43 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 25 Feb 2015 05:37:43 -0000 Authentication-Results: pb1.pair.com smtp.mail=francois@php.net; spf=unknown; sender-id=unknown Authentication-Results: pb1.pair.com header.from=francois@php.net; sender-id=unknown Received-SPF: unknown (pb1.pair.com: domain php.net does not designate 212.27.42.2 as permitted sender) X-PHP-List-Original-Sender: francois@php.net X-Host-Fingerprint: 212.27.42.2 smtp2-g21.free.fr Received: from [212.27.42.2] ([212.27.42.2:59175] helo=smtp2-g21.free.fr) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 4B/E1-32189-6AF5DE45 for ; Wed, 25 Feb 2015 00:37:42 -0500 Received: from moorea (unknown [82.240.16.115]) by smtp2-g21.free.fr (Postfix) with ESMTP id E93414B0083; Wed, 25 Feb 2015 06:37:21 +0100 (CET) Reply-To: To: "'Yasuo Ohgaki'" Cc: "'Alain Williams'" , References: <20150224093143.GC1891@phcomp.co.uk> <08b901d0508b$fb4ce060$f1e6a120$@php.net> In-Reply-To: Date: Wed, 25 Feb 2015 06:37:34 +0100 Message-ID: <08e101d050bd$290bbae0$7b2330a0$@php.net> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_08E2_01D050C5.8AD1F7A0" X-Mailer: Microsoft Outlook 14.0 Thread-Index: AQIPk8nXQdC7YxKTesF5vliHaD2pywJ92JufAaC3teMBfIVSwwMABov/nD14VcA= Content-Language: fr X-Antivirus: avast! (VPS 150224-1, 24/02/2015), Outbound message X-Antivirus-Status: Clean Subject: RE: [PHP-DEV] [Discussion] Last chance for case-sensitive engine From: francois@php.net (=?utf-8?Q?Fran=C3=A7ois_Laupretre?=) ------=_NextPart_000_08E2_01D050C5.8AD1F7A0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hi, =20 The most important point, IMO, is that it will be extremely complex to = provide a =E2=80=98deprecated=E2=80=99 transition step. =20 I won=E2=80=99t have time to work on it during the next month (will be = in Africa starting next Saturday). So feel free to take over the RFC and = propose something for the future. =20 Regards =20 Fran=C3=A7ois =20 De : yohgaki@gmail.com [mailto:yohgaki@gmail.com] De la part de Yasuo = Ohgaki Envoy=C3=A9 : mercredi 25 f=C3=A9vrier 2015 03:07 =C3=80 : francois Cc : Alain Williams; internals@lists.php.net Objet : Re: [PHP-DEV] [Discussion] Last chance for case-sensitive engine =20 Hi Francois, On Wed, Feb 25, 2015 at 8:45 AM, Fran=C3=A7ois Laupretre = wrote: > > I stopped for several reasons : > > 1. The reactions were mostly negative, with a majority of 'breaks = much, > brings nothing' opinions, > > 2. Crawling through the code, I discovered that code to handle case > insensitivity was spread all around PHP. Example: I thought that = function > and method names could be made case-sensitive by modifying a limited = number > of lines of code. Actually, it seems it is handled in a more or less > redundant way in a lot of locations. So, I quickly realized that > implementation would be extremely complex. > > 3. A lot of PHP code is, knowingly or not, using PHP case = insensitivity. > > 4. A patch to make PHP case sensitive would be very complex, and = providing a > two-mode mechanism still much more. It would require in many cases to > provide another case-sensitive test after each case-insensitive one = and > raise an error if both don't match. We must do that because = case-insensitive > comparisons are done using a case-sensitive comparison of two strings > previously converted to lowercase. It would also require to store = every > class/function/method names twice, as they are currently stored in = lowercase > form. As lowercase names are transmitted as strings around the code, = it is > very complex to keep the link with the original value. So, to = summarize, I > now consider that providing a compatibility 'notice-only' mode is > practically impossible. > > So, while it seemed attractive at first, I stopped working on it. Sounds reasonable.=20 Zend does comparison/conversion various places indeed. "Propose=20 & announce it now, then implement it PHP8" may work. We may get a=20 little simpler Engine for PHP8. Regards, -- Yasuo Ohgaki yohgaki@ohgaki.net ------=_NextPart_000_08E2_01D050C5.8AD1F7A0--