Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:79138
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain ajf.me designates 192.64.116.207 as permitted sender)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 8.1 \(1993\))
In-Reply-To: <CADajX4DHgR=oSV7a+WGWiQyk9ycruqjujkHmE=zDqzj2sUvUZA@mail.gmail.com>
Date: Mon, 24 Nov 2014 22:35:23 +0000
Cc: Sara Golemon <pollita@php.net>,
 PHP Internals <internals@lists.php.net>
Content-Transfer-Encoding: quoted-printable
Message-ID: <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>
To: Adam Harvey <aharvey@php.net>
Subject: Re: [PHP-DEV] [RFC] Unicode Escape Syntax
From: ajf@ajf.me (Andrea Faulds)


> On 24 Nov 2014, at 22:30, Adam Harvey <aharvey@php.net> wrote:
>=20
> On 24 November 2014 at 14:21, Sara Golemon <pollita@php.net> wrote:
>> On Mon, Nov 24, 2014 at 2:09 PM, Andrea Faulds <ajf@ajf.me> wrote:
>>> Here=E2=80=99s a new RFC: https://wiki.php.net/rfc/unicode_escape
>>>=20
>> I'm okay with producing UTF-8 even though our strings are technically
>> binary.  As you state, UTF-8 is the de-facto encoding, and =
recognizing
>> this is pretty reasonable.
>=20
> 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 =
source file is specified to be with declare(), so it matches the =
encoding of other 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 =
characters will only be supported by Unicode encodings=E2=80=A6 and of =
those, only UTF-8 is really in much use here anyway.

>> 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).
>=20
> 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 =
makes just as much sense within Unicode strings. There are plenty of =
cases (like the U+202E or ma=C3=B1ana examples in the RFC) where you=E2=80=
=99d want a Unicode escape in a Unicode string.

--
Andrea Faulds
http://ajf.me/