Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:100583 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 92262 invoked from network); 14 Sep 2017 13:16:52 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 14 Sep 2017 13:16:52 -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:14721] helo=localhost.localdomain) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 88/FC-19300-2418AB95 for ; Thu, 14 Sep 2017 09:16:51 -0400 Message-ID: <88.FC.19300.2418AB95@pb1.pair.com> To: internals@lists.php.net References: <3D.0C.10715.383F8B95@pb1.pair.com> <20b8b6fa-ec81-eba9-d33b-b54b815e9e5d@lsces.co.uk> In-Reply-To: <20b8b6fa-ec81-eba9-d33b-b54b815e9e5d@lsces.co.uk> Date: Thu, 14 Sep 2017 14:16:47 +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") "Lester Caine" wrote in message news:20b8b6fa-ec81-eba9-d33b-b54b815e9e5d@lsces.co.uk... > >On 14/09/17 10:20, Tony Marston wrote: >> Then unix came along and FUBAR'd everything. Any advantages of case >> sensitive systems are ALWAYS outweighed by their disadvantages. > >Unix predates Windows ... A minor detail. Windows followed all the previous OSes which I had used in being case insensitive, which makes unix the odd one out. Besides there are far more computers running Windows than unix, so unixx should not be used as the standard. > the use of such breaks as having spaces in >file names came from that development in addition to the line ending. >The RTTY machines needed a carriage return step followed by a line feed >which is why that was two steps initially. Not needed these days, but >still embeded from the early days. I also saw LF and CR being used independently in a driver for a daisywheel printer in the 1970s. The fact that both CR and LF are not needed these days should have been addressed by a common solution used by all OSes, and not each OS using a different solution. >UTF8 introduces a level of complexity and can be used used in many >places in PHP, but it does seem that there is no drive these days to >make the core a clean UTF8 environment. This should perhaps be addressed >again for PHP8? If UTF8 solves the problem, but has yet to be properly implemented in PHP, then the PHP implementation should be addressed. > But the additional problems that case-insensitive then >introduces may mean that all case-insensitivity has to be removed at >that point? What additional problems? When billions of people are used to living in a case-insensitive world and the only "problems" affect an insignificantly small number in an insignificantly small number of circumstances then the only proper solution is one that solves the problem for the small number without messing it up for the far larger number. -- Tony Marston