Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:52598
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.216.42 as permitted sender)
DomainKey-Status: bad
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :cc:content-type;
        b=r7yHKvtXdBFg6+nn1rO9cd9tXXhrz8Zm8sTEZXX6TAAAZA6fz1vNhtdiBaXriJ+qme
         jm8sKI6FuibS4kd/2+SEXpwmCvK6Nbwxeqk8gbFQEooSxJDX7IgEVGBM/e4erltznxPJ
         prE9RejnuVEZYZTXd5Rj7B+fLrWZPQ93/K/zE=
MIME-Version: 1.0
In-Reply-To: <4DE560D4.2010409@lerdorf.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>
Date: Tue, 31 May 2011 15:02:22 -0700
Message-ID: <BANLkTi=Djsmff+o+REMaqS+tFuwhgi3K+w@mail.gmail.com>
To: Rasmus <rasmus@lerdorf.com>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=20cf300faeb5fe1e3304a4998e0c
Subject: Re: [PHP-DEV] RFC: Short syntax for Arrays (redux)
From: birken@gmail.com (Dan Birken)

--20cf300faeb5fe1e3304a4998e0c
Content-Type: text/plain; charset=ISO-8859-1

Yes it does :)

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.

It just seems simpler that:
array(1, 2) equals [1, 2]
array(1 => 2) equals [1 => 2]

-Dan

On Tue, May 31, 2011 at 2:42 PM, Rasmus <rasmus@lerdorf.com> wrote:

> 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:
> >
> > php > print_r(json_decode(json_encode(array('a' => 'b'))));
> > stdClass Object
> > (
> >     [a] => b
> > )
> >
> > php > print_r(json_decode(json_encode(array('a', 'b'))));
> > Array
> > (
> >     [0] => a
> >     [1] => b
> > )
>
> 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.
>
> 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.
>
> -Rasmus
>

--20cf300faeb5fe1e3304a4998e0c--