Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:100582
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.161.171 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <20b8b6fa-ec81-eba9-d33b-b54b815e9e5d@lsces.co.uk>
References: <c7746903-2e3a-3e86-59c9-63483b244feb@gmx.de> <CAESVnVpUkM_W9xF+0Qt=2M61dGy40gtOehFo=U_F3gd87rmxrQ@mail.gmail.com>
 <3D.0C.10715.383F8B95@pb1.pair.com> <CAESVnVp6OKB64WuO9iKEP=L9-QrrFjS+kcoeKYKULRUff-RitQ@mail.gmail.com>
 <F1.A9.19300.DF94AB95@pb1.pair.com> <20b8b6fa-ec81-eba9-d33b-b54b815e9e5d@lsces.co.uk>
Date: Thu, 14 Sep 2017 09:10:08 -0400
Message-ID: <CAEUnE0c2_JUydWXyn=Xmtkgwmo_iCFQBOE1dh25m7hsD15oZxg@mail.gmail.com>
To: "internals@lists.php.net >> PHP internals" <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="001a1148add6edbb12055925fee3"
Subject: Re: [PHP-DEV] Deprecate and remove case-insensitive constants?
From: tendoaki@gmail.com (Michael Morris)

--001a1148add6edbb12055925fee3
Content-Type: text/plain; charset="UTF-8"

On Thu, Sep 14, 2017 at 8:33 AM, Lester Caine <lester@lsces.co.uk> wrote:

> 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?
>
>
*Cough*, *Cough*, PHP 6, *Cough*, *Cough*.

Comedy aside, Full UTF functionality was planned for PHP 6 and ended up
sinking the branch because it was way more complicated that anyone realized
at first. Someone involved with the development at that time can speak to
it more accurately - all I know is hearsay and conjecture.

--001a1148add6edbb12055925fee3--