Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:52601
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.160.42 as permitted sender)
DomainKey-Status: bad
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=subject:mime-version:content-type:from:in-reply-to:date:cc
         :content-transfer-encoding:message-id:references:to:x-mailer;
        b=HGjvLoflGIpALWqMBbQmJlvgoTY9gMztyMiocDeWKUEPSlifZeXp9Ry+Q/tEvU0BBY
         1r3MCasnGbkC52N8bud2yd7zf+xbynqnGhleHCyjfJoL2bBPb/huxMCCKuVNoBFpT9aq
         HBbmcBiw7q0ogsd7jFsG3tTLm78Xj9UgEoR7s=
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
In-Reply-To: <BANLkTi=Djsmff+o+REMaqS+tFuwhgi3K+w@mail.gmail.com>
Date: Tue, 31 May 2011 17:02:59 -0500
Cc: Rasmus <rasmus@lerdorf.com>,
 PHP internals <internals@lists.php.net>
Content-Transfer-Encoding: quoted-printable
Message-ID: <45513D8B-9EA4-429F-8C8E-2521465CB98A@gmail.com>
References: <4DE5368A.6050603@moonspot.net> <2BFFEAC1-395E-4101-9452-002E63DCFD91@seancoates.com> <4DE55AB7.9050206@lerdorf.com> <4DE55CDA.302@sugarcrm.com> <BANLkTinoriGzfO7YzM+ov_Z0i50g=m8q6Q@mail.gmail.com> <4DE560D4.2010409@lerdorf.com> <BANLkTi=Djsmff+o+REMaqS+tFuwhgi3K+w@mail.gmail.com>
To: Dan Birken <birken@gmail.com>
Subject: Re: [PHP-DEV] RFC: Short syntax for Arrays (redux)
From: shadda@gmail.com (Matt Wilson)

Exactly my point. Why try to fudge json into php, instead of just =
improving php?

On May 31, 2011, at 5:02 PM, Dan Birken wrote:

> Yes it does :)
>=20
> I guess my point was it would be confusing if PHP supported JSON-like
> syntax, but json_decode(X) was different from eval(X).  So if PHP =
isn't
> going to use JSON syntax (because it doesn't work for assoc arrays), =
then I
> don't think there is much benefit in using *almost* JSON syntax.
>=20
> It just seems simpler that:
> array(1, 2) equals [1, 2]
> array(1 =3D> 2) equals [1 =3D> 2]
>=20
> -Dan
>=20
> On Tue, May 31, 2011 at 2:42 PM, Rasmus <rasmus@lerdorf.com> wrote:
>=20
>> On 05/31/2011 02:34 PM, Dan Birken wrote:
>>> It is worth noting that point you bring up is one that is present in =
PHP
>>> currently:
>>>=20
>>> php > print_r(json_decode(json_encode(array('a' =3D> 'b'))));
>>> stdClass Object
>>> (
>>>    [a] =3D> b
>>> )
>>>=20
>>> php > print_r(json_decode(json_encode(array('a', 'b'))));
>>> Array
>>> (
>>>    [0] =3D> a
>>>    [1] =3D> b
>>> )
>>=20
>> Sure, but that makes makes perfect sense, does it not? Javascript =
does
>> not have associative arrays. So any non-scalar array has to be mapped =
to
>> a Javascript object in order to be represented. When we bring it back =
we
>> map a Javascript object to a PHP object, however, there is an =
optional
>> argument on json_decode() to change that to an associative array if
>> desired.
>>=20
>> The point we are making is that this exact inability of the json
>> notation to distinguish an associative array from an object makes it =
a
>> problematic choice for a native syntax in PHP.
>>=20
>> -Rasmus
>>=20