Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:100610 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 80174 invoked from network); 15 Sep 2017 09:02:48 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 15 Sep 2017 09:02:48 -0000 X-Host-Fingerprint: 62.31.75.76 76.75-31-62.static.virginmediabusiness.co.uk Received: from [62.31.75.76] ([62.31.75.76:29333] helo=localhost.localdomain) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 33/29-19300-7379BB95 for ; Fri, 15 Sep 2017 05:02:48 -0400 Message-ID: <33.29.19300.7379BB95@pb1.pair.com> To: internals@lists.php.net References: <3D.0C.10715.383F8B95@pb1.pair.com> <1505382004.4078127.1105791680.3A06C2FA@webmail.messagingengine.com> <16.4C.19300.B2D7AB95@pb1.pair.com> <98ab178e-b999-7e36-5ff5-7b8c28fe0dd4@gmx.de> <02.9E.19300.FD58AB95@pb1.pair.com> <20170914134603.GS8096@phcomp.co.uk> In-Reply-To: <20170914134603.GS8096@phcomp.co.uk> Date: Fri, 15 Sep 2017 10:02:43 +0100 Lines: 1 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="utf-8"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal Importance: Normal X-Newsreader: Microsoft Windows Live Mail 16.4.3564.1216 X-MimeOLE: Produced By Microsoft MimeOLE V16.4.3564.1216 X-Posted-By: 62.31.75.76 Subject: Re: [PHP-DEV] Deprecate and remove case-insensitive constants? From: TonyMarston@hotmail.com ("Tony Marston") "Alain Williams" wrote in message news:20170914134603.GS8096@phcomp.co.uk... > >On Thu, Sep 14, 2017 at 02:36:27PM +0100, Tony Marston wrote: >> ""Christoph M. Becker"" wrote in message >> news:98ab178e-b999-7e36-5ff5-7b8c28fe0dd4@gmx.de... >> > >> >On 14.09.2017 at 14:59, Tony Marston wrote: >> > >> >>Introducing case sensitivity into what is mostly a case-insensitive >> >>world just for the convenience of a few programmers I do not consider >> >>to >> >>be acceptable. It would cause more problems for far more people than >> >>the >> >>insignificant few who insist on using obscure character sets. Why >> >>should >> >>the English-speaking world be forced to suffer just because some minor >> >>languages cannot handle case folding? >> > >> >This is not about an "insignificant few who insist on using obscure >> >character sets", but rather about a language spoken by millions of >> >people which has to "I" characters, namely dotted and dotless "I". >> >Rather consistently, the dotless "I"'s lower-case variant is "i", and >> >the dotted "I"'s lower-case variant is "i". There you go. >> > >> >> The number of people in the world who use character sets which do >> not have this problem far outnumber those who use character sets >> which do have this problem. People without this problem far >> outnumber the others, so it would not be a good idea to >> inconvenience the many just to satisfy the few. > >Translation: I do not use these character sets, those who do are not >important. Incorrect. The proper question is: How any character sets have this problem? What percentage of the world's computer users are affected by this problem? If this number is quite small then it would be wrong to make the majority suffer just because you don't know how to fix the problem that affects the minority. >PHP (& File systems) are best staying away from things like that. Microsoft produces case insensitive software, including file systems, because that is what users are used to. Unix was invented in a laboratory by academics who couldn't develop case insensitive software so they called it a "feature" and not a "bug". > Not attempting >case folding, and similar, makes it simpler, faster & more robust (not >worrying >about what sort of 'i' to convert to). It only helps those who do not know >what >the SHIFT key is for. Why is it not possible to identify a single upper and lower case variant for every character in every character set? -- Tony Marston