Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:79829
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain ajf.me designates 192.64.116.216 as permitted sender)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 8.1 \(1993\))
In-Reply-To: <20141220225219.GH11370@phcomp.co.uk>
Date: Sat, 20 Dec 2014 22:55:02 +0000
Cc: internals@lists.php.net
Content-Transfer-Encoding: quoted-printable
Message-ID: <E20D0D76-70E3-44C2-B191-F4A11A617E70@ajf.me>
References: <000c01d01ca0$7e70c850$7b5258f0$@yahoo.fr> <EE790D15-E5B9-4556-AB9A-EEF17FC45503@ajf.me> <20141220225219.GH11370@phcomp.co.uk>
To: Alain Williams <addw@phcomp.co.uk>
Subject: Re: [PHP-DEV] Proposal for PHP 7 : case-sensitive symbols
From: ajf@ajf.me (Andrea Faulds)

Hey Alain,

> On 20 Dec 2014, at 22:52, Alain Williams <addw@phcomp.co.uk> wrote:
>=20
> On Sat, Dec 20, 2014 at 10:45:39PM +0000, Andrea Faulds wrote:
>=20
>> 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=E2=80=99d mean constants, variable =
names and properties would need changing, everything else is already =
case-insensitive.=20
>=20
> 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.

That=E2=80=99s true. Although mixing English and another language in =
source code isn=E2=80=99t a terribly good idea anyway.

> 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.

This isn=E2=80=99t that unusual among BC breaks, honestly.

Thanks.
--
Andrea Faulds
http://ajf.me/