Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:52877
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.213.170 as permitted sender)
DomainKey-Status: bad
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:from:date:message-id:subject:to:content-type;
        b=F9iRrkYvf2CM8XtSbGJgu+DQkrlTCQMskK4okUM09NcLZIbtToi0j0HDJHHskTgMC3
         2N7Kt8uFEtGMEHLLJaMTq+35p1UIuA397iP1doM9rNoWPGWMMOwkIK0aq7tR0lXPDsaJ
         Hz6N0rbZUrdp90Pl7zp9Fv3rLEkPlFtVNiRyU=
MIME-Version: 1.0
Date: Fri, 3 Jun 2011 20:17:36 -0500
Message-ID: <BANLkTimxaaMTbWyhs=0tnZiCGyPwAsARqA@mail.gmail.com>
To: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=005045015be8dfed1504a4d8a3e6
Subject: JSON array/object syntax
From: dukeofgaming@gmail.com (dukeofgaming)

--005045015be8dfed1504a4d8a3e6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi,

After reading all the debate in the other thread it is still not clear to m=
e
what the real advantages are of adopting JSON syntax for native PHP
types. Doing json_encode to an object and expect the code and output to be
the same seems useless to me, and reading David Z=FClke's example it seems
more like a pure-unicode issue to me:

----

It is different from writing json_decode('=E4\u0123'), because json_decode(=
)
in PHP only accepts UTF-8 encoded input;

Give it a shot:

<?php
$chr =3D "\xC3\xA4"; // "=E4" as UTF-8
var_dump(json_decode('["' . $chr . '\u00e4"]'));
var_dump(json_decode('["' . utf8_decode($chr) . '\u00e4"]'));
?>

That'll produce:

> array(1) {
>   [0]=3D>
>   string(4) "=E4=E4"
> }
> NULL

Understand what the problem is now?

If someone does this in a latin1-encoded file:

<?php $fancyNewArray =3D {"yay": "=E4"}; ?>

Then that is valid as a PHP array (as it's a latin1 "=E4", so \xE4), but
cannot be consumed by PHP's json_decode(). And that would be terribly
inconsistent behavior.

-----

It looks more like you want to do json_decode to PHP code hoping that will
somehow fix json_decode... instead of fixing json_decode.

Could someone advocating this please explain with use-cases and concrete &
punctualized examples the advantages of having such JSON approach to PHP.

Regards,

David Vega

--005045015be8dfed1504a4d8a3e6--