Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:83734 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 22344 invoked from network); 25 Feb 2015 02:07:45 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 25 Feb 2015 02:07:45 -0000 Authentication-Results: pb1.pair.com header.from=yohgaki@gmail.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=yohgaki@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.216.45 as permitted sender) X-PHP-List-Original-Sender: yohgaki@gmail.com X-Host-Fingerprint: 209.85.216.45 mail-qa0-f45.google.com Received: from [209.85.216.45] ([209.85.216.45:43172] helo=mail-qa0-f45.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 9D/92-24698-07E2DE45 for ; Tue, 24 Feb 2015 21:07:44 -0500 Received: by mail-qa0-f45.google.com with SMTP id j7so729856qaq.4 for ; Tue, 24 Feb 2015 18:07:41 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=aPz4PVKBwDbKor5OA9ppYD/u93M0fPkTEkGzQHO3H3s=; b=BUsEThrqF04Na+CzKynt6j41SmVOTCoRjcjO10r1H0SFw1gmkAOz8VpxyO7sV0xX58 umbxj7P3XgQEpr3XqbKd68unIi6njp+NVsAVW6G4mpxPe6+YCvsUAwezX0DhULPmaBaj FhKGhFeaVK0QFHly4iF9/sD9gZ7qOT1Thwggzs5FNc9Q3PO4WExgw/xBhtnxXRHKUDoB vI8TaZ6C2g8BGJhsd+JSNT+64Y+9MJIIkbRWjWG/I4VVp4wlld3fCLGCBGUryx4bWY6I LZH1GdqDrQ+gwwvFAxTYq9QmWQ3fPwa4gB5Ob31mqwF3yW+5GxCO9ZEK+izmjilewJfQ iaBw== X-Received: by 10.140.17.9 with SMTP id 9mr1872687qgc.21.1424830061782; Tue, 24 Feb 2015 18:07:41 -0800 (PST) MIME-Version: 1.0 Sender: yohgaki@gmail.com Received: by 10.229.198.8 with HTTP; Tue, 24 Feb 2015 18:07:01 -0800 (PST) In-Reply-To: <08b901d0508b$fb4ce060$f1e6a120$@php.net> References: <20150224093143.GC1891@phcomp.co.uk> <08b901d0508b$fb4ce060$f1e6a120$@php.net> Date: Wed, 25 Feb 2015 11:07:01 +0900 X-Google-Sender-Auth: fNgcJLnxni2xwwsONsrDZX8K9Vc Message-ID: To: francois Cc: Alain Williams , "internals@lists.php.net" Content-Type: multipart/alternative; boundary=001a11c0b36ab2acbe050fe01957 Subject: Re: [PHP-DEV] [Discussion] Last chance for case-sensitive engine From: yohgaki@ohgaki.net (Yasuo Ohgaki) --001a11c0b36ab2acbe050fe01957 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable 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 i= s > 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. Zend does comparison/conversion various places indeed. "Propose & announce it now, then implement it PHP8" may work. We may get a little simpler Engine for PHP8. Regards, -- Yasuo Ohgaki yohgaki@ohgaki.net --001a11c0b36ab2acbe050fe01957--