Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:79135
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: softfail (pb1.pair.com: domain golemon.com does not designate 209.85.192.177 as permitted sender)
MIME-Version: 1.0
Sender: php@golemon.com
In-Reply-To: <C2A085AA-3E3A-405F-954B-4C1F68A46012@ajf.me>
References: <C2A085AA-3E3A-405F-954B-4C1F68A46012@ajf.me>
Date: Mon, 24 Nov 2014 14:21:37 -0800
Message-ID: <CAESVnVo=mHD1yNSdmHAaho4Emg2qLLB6hrb_pvVXo8h68-OpVw@mail.gmail.com>
To: Andrea Faulds <ajf@ajf.me>
Cc: 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: pollita@php.net (Sara Golemon)

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
>
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.

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).

On the BMP versus SMP issue of \uXXXX styles, we addressed this in
PHP6 by making \u denote 4 hexit BMP codepoints, while \U denoted six
hexit codepoints.   e.g.    "\u1234" =3D=3D=3D "\U001234"   I'd rather
follow this style than making \u special and different from hex and
octal notations by using braces.

-Sara