Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:79139
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain adamharvey.name designates 209.85.223.179 as permitted sender)
MIME-Version: 1.0
Sender: adam@adamharvey.name
In-Reply-To: <13B08117-4BE5-4E0D-A3FF-B6A4D1F9584C@ajf.me>
References: <C2A085AA-3E3A-405F-954B-4C1F68A46012@ajf.me> <CAESVnVo=mHD1yNSdmHAaho4Emg2qLLB6hrb_pvVXo8h68-OpVw@mail.gmail.com>
 <CADajX4DHgR=oSV7a+WGWiQyk9ycruqjujkHmE=zDqzj2sUvUZA@mail.gmail.com> <13B08117-4BE5-4E0D-A3FF-B6A4D1F9584C@ajf.me>
Date: Mon, 24 Nov 2014 14:41:19 -0800
Message-ID: <CADajX4CX=KyJm7xOuLj4ZjcPjv3+Hn=X8-cLg2Ri-yv7gr5xiQ@mail.gmail.com>
To: Andrea Faulds <ajf@ajf.me>
Cc: Sara Golemon <pollita@php.net>, PHP Internals <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] [RFC] Unicode Escape Syntax
From: aharvey@php.net (Adam Harvey)

On 24 November 2014 at 14:35, Andrea Faulds <ajf@ajf.me> wrote:
>
>> On 24 Nov 2014, at 22:30, Adam Harvey <aharvey@php.net> wrote:
>> I'm also OK with this, although I do wonder if we should be respecting
>> the user's default_charset setting instead. (Since default_charset
>> defaults to "UTF-8", in practice this isn't a significant difference
>> for the average user.)
>
> Ooh, that would be a possibility. That or using whatever encoding the sou=
rce file is specified to be with declare(), so it matches the encoding of o=
ther characters in the string.
>
> This=E2=80=99d add significant complexity to it, though (would we have to=
 require ICU or something? D:), plus the vast majority of Unicode character=
s will only be supported by Unicode encodings=E2=80=A6 and of those, only U=
TF-8 is really in much use here anyway.

We would have to require ICU, but that might be worthwhile for PHP 7
anyway. Having at least one i18n API that's guaranteed to be available
would be nice.

>>> You may want to make it a requirement that strings containing \u
>>> escapes are denoted as:   u"blah blah"    We set aside this format
>>> back in the PHP6 days (note that b"blah" is equivalent to "blah" for
>>> binary strings).
>>
>> It seems to me that the point of \u and \U escapes is to embed Unicode
>> in potentially non-Unicode strings, so using u"" doesn't feel right.
>
> I don=E2=80=99t really see where you=E2=80=99re coming from, it also make=
s just as much sense within Unicode strings. There are plenty of cases (lik=
e the U+202E or ma=C3=B1ana examples in the RFC) where you=E2=80=99d want a=
 Unicode escape in a Unicode string.

I probably worded that badly =E2=80=94 I just mean that I don't think \u an=
d
\U should be limited to only u"" strings, but should work in normal
strings as well. (In other words, I'm agreeing with what's in your
RFC, not with Sara.)

Adam