On Mon, Nov 24, 2014 at 02:21:37PM -0800, Sara Golemon wrote:
> On Mon, Nov 24, 2014 at 2:09 PM, Andrea Faulds <a...@ajf.me> wrote:
> > Here’s 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" === "\U001234" I'd rather
> follow this style than making \u special and different from hex and
> octal notations by using braces.
There is a big difference with \u or \U and \x or \o and that is the number of
characters that follow the escape. \x has 2, \o has 3 - both are short and easy
to count with the eye. \U012345 is quite long and it is not so visually obvious
where it should end.
Ergo: I prefer Andrea's "\u{0123}" as it is going to be more robust against
typos.
One other thing that we could do is to allow code points to be named, with \U
(capital 'U') eg:
echo "\U{arabic letter alef}\n";
If you think that it is a bad idea, please update the RFC to say why this is a
bad idea and so why it is not going to happen - for now.
It would be nice since a code point is just a big number without any really
obvious
meaning, but a name makes for greater clarity.
However: I suspect that interpretting this might be considerably slower which
means slower compilation.
Regards
--
Alain Williams
Linux/GNU Consultant - Mail systems, Web sites, Networking, Programmer, IT
Lecturer.
+44 (0) 787 668 0256 http://www.phcomp.co.uk/
Parliament Hill Computers Ltd. Registration Information:
http://www.phcomp.co.uk/contact.php
#include <std_disclaimer.h>
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
