Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:18187
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
To: andrei@gravitonic.com (Andrei Zmievski)
Cc: internals@lists.php.net
Date: Tue, 16 Aug 2005 23:57:27 +0200
Message-ID: <57n4g11mj3g0f14huvvmcq852pis23oeop@4ax.com>
References: <937066F0-AA5F-41E2-99A0-D74C7F44FFCA@gravitonic.com>
In-Reply-To: <937066F0-AA5F-41E2-99A0-D74C7F44FFCA@gravitonic.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: Re: PHP Unicode support design document
From: php@ter.dk (Peter Brodersen)

On Wed, 10 Aug 2005 00:31:30 -0700, in php.internals
andrei@gravitonic.com (Andrei Zmievski) wrote:

>  - existing PHP escape sequences are also interpreted as Unicode =
codepoints,
>    including \xXX (hex) and \OOO (octal) numbers, e.g. "\x20" =3D> =
U+0020
[..]
>The single-quoted string is more restrictive than the other two types: =
so
>far the only escape sequence allowed inside of it was \', which =
specifies
>a literal single quote. However, single quoted strings now support the =
new
>Unicode character escape sequences as well.

=46or what it's worth, would \1 be interpreted as well in single quotes
(as it currently is in double quotes)?

I suppose one of the places where \digit would be present in several
cases is in poor-written pregs - such as:
	print preg_replace('/([A-Z])/','<b>\1</b>',$string);
(where \1 is used as backreference instead of \\1 or $1)

I'm not that worried about my own preg-usage. I just want to be
prepared if I ever have to review some code for the purpose of
migrating to PHP6.

--=20
- Peter Brodersen