Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:79828
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain phcomp.co.uk designates 78.32.209.33 as permitted sender)
Date: Sat, 20 Dec 2014 22:52:19 +0000
To: internals@lists.php.net
Message-ID: <20141220225219.GH11370@phcomp.co.uk>
Mail-Followup-To: internals@lists.php.net
References: <000c01d01ca0$7e70c850$7b5258f0$@yahoo.fr>
 <EE790D15-E5B9-4556-AB9A-EEF17FC45503@ajf.me>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <EE790D15-E5B9-4556-AB9A-EEF17FC45503@ajf.me>
Organization: Parliament Hill Computers Ltd
User-Agent: Mutt/1.5.20 (2009-12-10)
Subject: Re: [PHP-DEV] Proposal for PHP 7 : case-sensitive symbols
From: addw@phcomp.co.uk (Alain Williams)

On Sat, Dec 20, 2014 at 10:45:39PM +0000, Andrea Faulds wrote:

> I would like to see more case uniformity, but I think this is the less practical direction. Instead of making everything case-sensitive, we should make everything case-insensitive, which would break far less stuff, and is a smaller change. That’d mean constants, variable names and properties would need changing, everything else is already case-insensitive. 

As I said: this is only partly true; true if you are a Brit or a Yank ...
everyone else who has alphabetics that are represented by bytes with the top bit
set sees them as case sensitive in those parts.

It is a BC break, but a very unusual one in that once code is fixed in, say PHP
7, it would continue to work when copies back to a PHP 5 environment.

-- 
Alain Williams
Linux/GNU Consultant - Mail systems, Web sites, Networking, Programmer, IT Lecturer.
+44 (0) 787 668 0256  http://www.phcomp.co.uk/
Parliament Hill Computers Ltd. Registration Information: http://www.phcomp.co.uk/contact.php
#include <std_disclaimer.h>