Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:102590
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.223.174 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CAEsg9X2O9xii3J4iC2f+Z7g-aje+mCRZ2j=6P8=uyqqa0k=Uyg@mail.gmail.com>
References: <CAEsg9X2O9xii3J4iC2f+Z7g-aje+mCRZ2j=6P8=uyqqa0k=Uyg@mail.gmail.com>
Date: Thu, 5 Jul 2018 00:01:52 +0200
Message-ID: <CAF+90c9WDBgB1N3AUUUwY5u+gYps0=KKFHRgWK_RME7OrbFmtw@mail.gmail.com>
To: David Rodrigues <david.proweb@gmail.com>
Cc: PHP Internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="00000000000005ada9057033948a"
Subject: Re: [PHP-DEV] json_encode() x-notation
From: nikita.ppv@gmail.com (Nikita Popov)

--00000000000005ada9057033948a
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Fri, Jun 29, 2018 at 8:51 PM, David Rodrigues <david.proweb@gmail.com>
wrote:

> =E2=80=8BHello. I saw that JS supports the x-notation (\x40) and u-notati=
on
> (\u0040), but PHP only supports u-notation. There some reason for that?
>
> JSON.parse('"\x40"'); // =3D> @
> JSON.parse('"\u0040"'); // =3D> @
>

No it doesn't. JSON.parse() will correctly reject \x escapes because they
aren't valid JSON. You are using a normal JS string (which has nothing to
do with JSON and supports \x), which will unescape \x before JSON.parse()
ever sees it. If you write JSON.parse('"\\x40"') or similar, you will get
an error.

Nikita

--00000000000005ada9057033948a--