Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:72716
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.216.44 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <69AB9D0D-FF9E-42BE-B91C-827F7810B0F6@ajf.me>
References: <69AB9D0D-FF9E-42BE-B91C-827F7810B0F6@ajf.me>
Date: Thu, 20 Feb 2014 17:23:56 +0100
Message-ID: <CAEZPtU7tUmLyh97_1FLcOnnSTmRO+pACu8_BMaDG13CEt-Dy1A@mail.gmail.com>
To: Andrea Faulds <ajf@ajf.me>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=047d7beb961e916e3104f2d8ee27
Subject: Re: [PHP-DEV] Simpler Unicode solution for PHP6
From: pierre.php@gmail.com (Pierre Joye)

--047d7beb961e916e3104f2d8ee27
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi,

On Feb 20, 2014 11:17 PM, "Andrea Faulds" <ajf@ajf.me> wrote:
>
> Hi,
>
> As a simpler to implement approach to Unicode, could we perhaps support
it just by adding an =E2=80=9Cis UTF-8=E2=80=9D flag to strings internally?=
 Then unmodified
functions would just see a normal string and handle it like they do any
other, and modified and new Unicode-aware functions would test for the
presence of the flag and handle the string appropriately in that case.
>
> Thoughts?

That could be an option during the development phase. However I do not like
the idea of a flag for the final implementation, it creates more troubles
from an application point of view.

The main problem remains tho' (see the other threads). If we do not manage
to solve it within the next months, we can delay 6 for another year or two.

Cheers,
Pierre

--047d7beb961e916e3104f2d8ee27--