Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:41772 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 41671 invoked from network); 8 Nov 2008 09:34:01 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 8 Nov 2008 09:34:01 -0000 Authentication-Results: pb1.pair.com smtp.mail=lester@lsces.co.uk; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=lester@lsces.co.uk; sender-id=unknown Received-SPF: error (pb1.pair.com: domain lsces.co.uk from 213.123.20.123 cause and error) X-PHP-List-Original-Sender: lester@lsces.co.uk X-Host-Fingerprint: 213.123.20.123 c2bthomr05.btconnect.com Received: from [213.123.20.123] ([213.123.20.123:21007] helo=C2bthomr05.btconnect.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id B6/32-18522-40D55194 for ; Sat, 08 Nov 2008 04:33:58 -0500 Received: from [127.0.0.1] (host81-138-11-136.in-addr.btopenworld.com [81.138.11.136]) by C2bthomr05.btconnect.com with ESMTP id IXM22261; Sat, 8 Nov 2008 09:33:52 GMT Message-ID: <49155D01.9060104@lsces.co.uk> Date: Sat, 08 Nov 2008 09:33:53 +0000 User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.17) Gecko/20080829 SeaMonkey/1.1.12 MIME-Version: 1.0 To: "internals >> PHP internals" References: <8FBBAB3F-D20A-4FA1-9D17-869DABB88721@pooteeweet.org> In-Reply-To: <8FBBAB3F-D20A-4FA1-9D17-869DABB88721@pooteeweet.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Junkmail-Status: score=10/50, host=C2bthomr05.btconnect.com X-Junkmail-SD-Raw: score=unknown, refid=str=0001.0A090205.49155D01.0133,ss=1,fgs=0, ip=127.0.0.1, so=2007-10-30 19:00:17, dmn=5.7.1/2008-09-02 X-Junkmail-IWF: false Subject: Re: [PHP-DEV] Case sensitivity From: lester@lsces.co.uk (Lester Caine) Lukas Kahwe Smith wrote: > > On 06.11.2008, at 18:46, Stan Vassilev | FM wrote: > >> NOTE: Continuing from thread "Call it: allow reserved words in a class >> or not?": >> >>> As much as I'd love to see more case-sensitivity, I'm afraid it would >>> break quite a lot of existing apps, according to Google Code. >>> >>> http://www.google.com/codesearch?q=lang%3Aphp+%3D%5Cs%2AArray >>> >>> -JD >> >> It's worse than I thought, really out of the question for 5.x. >> >> Though I still think it's something we should consider for 6.0 as it's >> something we need to fix in the long term (and 6.0 already has breaks, >> such as strings used in binary operations need to be changed to binary >> strings). >> >> I can provide a short PHP script which can automatically fix the case >> of internal classes and keywords like array() in most source code out >> there. >> >> We can test such automated porting scripts on samples collected from >> PEAR, Google Code and projects like Drupal, Joomla etc. to reduce side >> effects. > > NO! Is that to any move to case sensitivity? Even if it is the tidiest way of plugging some of the holes in a clean UTF8 implementation via 6.0 where 'lower' or 'upper' may produce different results? Personally I've always worked with maintaining case - C++ dictates it - so it's natural to ensure that a case-sensitive search always provides the correct results. I'll even correct code that differs .... -- Lester Caine - G8HFL ----------------------------- Contact - http://lsces.co.uk/lsces/wiki/?page=contact L.S.Caine Electronic Services - http://lsces.co.uk EnquirySolve - http://enquirysolve.com/ Model Engineers Digital Workshop - http://medw.co.uk// Firebird - http://www.firebirdsql.org/index.php