Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:79148
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain zend.com designates 209.85.220.172 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <C2A085AA-3E3A-405F-954B-4C1F68A46012@ajf.me>
References: <C2A085AA-3E3A-405F-954B-4C1F68A46012@ajf.me>
Date: Tue, 25 Nov 2014 12:33:01 +0400
Message-ID: <CA+9eiLsNHZMTgV0EZFXxYmAx+sE-qbgPrTYE0rH=bFLpSq2rdg@mail.gmail.com>
To: Andrea Faulds <ajf@ajf.me>
Cc: PHP Internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=089e0111d0cc5bb6a50508aac2be
Subject: Re: [PHP-DEV] [RFC] Unicode Escape Syntax
From: dmitry@zend.com (Dmitry Stogov)

--089e0111d0cc5bb6a50508aac2be
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

May be I misunderstood something, but why to introduce unicode escapes if
PHP engine doesn't support Unicode.

Always converting such escapes into UTF-8 encoding, doesn't make any sense
for people who use other encodings for output, databases, etc.

Thanks. Dmitry.




On Tue, Nov 25, 2014 at 1:09 AM, Andrea Faulds <ajf@ajf.me> wrote:

> Good evening,
>
> Here=E2=80=99s a new RFC: https://wiki.php.net/rfc/unicode_escape
>
> It has a rationale section explaining why certain decisions were made,
> that I=E2=80=99d recommend you read in full.
>
> Thanks!
> --
> Andrea Faulds
> http://ajf.me/
>
>
>
>
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>

--089e0111d0cc5bb6a50508aac2be--