Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:102531
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.214.41 as permitted sender)
MIME-Version: 1.0
Date: Fri, 29 Jun 2018 15:51:15 -0300
Message-ID: <CAEsg9X2O9xii3J4iC2f+Z7g-aje+mCRZ2j=6P8=uyqqa0k=Uyg@mail.gmail.com>
To: PHP Internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="000000000000c3ea69056fcc55f3"
Subject: json_encode() x-notation
From: david.proweb@gmail.com (David Rodrigues)

--000000000000c3ea69056fcc55f3
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

=E2=80=8BHello. I saw that JS supports the x-notation (\x40) and u-notation
(\u0040), but PHP only supports u-notation. There some reason for that?

JSON.parse('"\x40"'); // =3D> @
JSON.parse('"\u0040"'); // =3D> @

While PHP:

json_decode('"\\u0040"'); // =3D> @
json_decode('"\\x40"'); // =3D> null (Syntax error)

The json.org really don't seems doc the x-notation version, but some pages
does: http://www.javascriptkit.com/jsref/escapesequence.shtml

The same is valid to json_encode('@'), it will stringify to '\u0040'
instead of the most simplified version '\x40'.

I don't know if there are some reason for that, but I think that, at least,
is reasonable to json_decode() supports that.

--=20
David Rodrigues

--000000000000c3ea69056fcc55f3--