Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:79847
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.53 as permitted sender)
User-Agent: K-9 Mail for Android
In-Reply-To: <20141220224424.GG11370@phcomp.co.uk>
References: <000c01d01ca0$7e70c850$7b5258f0$@yahoo.fr> <20141220224424.GG11370@phcomp.co.uk>
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Content-Type: text/plain;
 charset=UTF-8
Date: Sun, 21 Dec 2014 12:55:38 +0000
To: Alain Williams <addw@phcomp.co.uk>,internals@lists.php.net
Message-ID: <DBCE4E9D-209B-4020-86D3-360654025330@gmail.com>
Subject: Re: [PHP-DEV] Proposal for PHP 7 : case-sensitive symbols
From: rowan.collins@gmail.com (Rowan Collins)

On 20 December 2014 22:44:24 GMT, Alain Williams <addw@phcomp.co.uk> wrote:
>Fixing this would require a lot of work as well as some way of
>determining what
>character encoding the source file was written in ... different
>includes might
>have different encodings.
>
>We recently talked about a way of specifying source file encoding and
>decided
>that it was not something to look at now (IIRC).

I haven't read the whole thread yet, so apologies if someone's mentioned this already, but far from being a rejected feature, specifying source file encoding is already possible, using declare(encoding=...)

The problem is what to do with that information: presumably, identifiers would need to be converted to an internal encoding (prob utf8), case folded, and normalised (in the Unicode sense of that term). Ideally, this would happen during compilation and stored appropriately in the OpCache, but a run-time path for userland strings would also be necessary.