Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:52792
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.220.170 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=HzsOsFBUximDll9ugjY202kh/V5ovUoA4NEkdhXY5is7ZWUwWs71nYRAIl8HOdXlxt
         /BVvOcpDr4ktcr7WpVOtig1X+WP0axqz3EyHSfQUMoVqHk5pWGbTvkDE4l4mw0tmtcWp
         JGcu3HvUJAGfd1qFMV5/7ZIeMejoZG0YdSWM8=
MIME-Version: 1.0
In-Reply-To: <F2B65D81-CD84-45E3-B4BE-DB7E41CE3BEF@seancoates.com>
References: <4DE5368A.6050603@moonspot.net>
	<BANLkTikKe8qWfjkEnANo9p5=8s=JdcHujw@mail.gmail.com>
	<BANLkTi=Y=P-O=ZRtUzjQ5i3anE=h9PF7Bg@mail.gmail.com>
	<BANLkTi=YrZbBkFubHx48K=YeEhHi9eXj2A@mail.gmail.com>
	<8BEEEE49-8DA3-4634-BF9C-120F7A15B613@roshambo.org>
	<BANLkTi=ETnz8g53WwOmL-uZCBWzokPMrZQ@mail.gmail.com>
	<BANLkTikrkRbEqOfZUFio__GCwnoTKf966g@mail.gmail.com>
	<BANLkTinWpCQRcrsn+o0w-M4ar58VVSBXNw@mail.gmail.com>
	<EB840916-64F2-44D0-AB3C-73679661CF73@justincarmony.com>
	<BANLkTinLCuHiKEAiGTQHfA4riHfXy4npkA@mail.gmail.com>
	<F2B65D81-CD84-45E3-B4BE-DB7E41CE3BEF@seancoates.com>
Date: Thu, 2 Jun 2011 13:04:41 -0300
Message-ID: <BANLkTikrMMQV+fJHFy7FxoqA688edE4psA@mail.gmail.com>
To: Sean Coates <sean@seancoates.com>
Cc: Anthony Ferrara <ircmaxell@gmail.com>, PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=90e6ba53b0707ffbc404a4bccb2b
Subject: Re: [PHP-DEV] RFC: Short syntax for Arrays (redux)
From: martinscotta@gmail.com (Martin Scotta)

--90e6ba53b0707ffbc404a4bccb2b
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

Could we first go out with fully JSON compatible version for 5.4?
and then later decide the =3D> stuff based on how that worked.

Native JSON is a big stuff for userland, and I'm pretty sure it will bring =
a
hole of core version upgrades.

 Martin Scotta


On Wed, Jun 1, 2011 at 7:09 PM, Sean Coates <sean@seancoates.com> wrote:

> > Now, the only reason I would personally support the array shortcut is
> > if it was an implementation of JSON.  I know that's not on the table
> > here
>
> I don't think anything is officially off the table, unless we forego
> discussion.
>
> My application is largely JSON-powered. We pass data from back- to
> front-end via JSON, we interact with MongoDB via the extension (which is =
an
> altered JSON-like protocol (arrays instead of objects), but would be a lo=
t
> more fluent with actual objects=97they're just too hard to make in curren=
t
> PHP), and we interface with ElasticSearch. The paste I linked earlier is =
our
> primary ElasticSearch query.
>
> The benefits of first-class JSON are important and wide-reaching;
> especially when interacting with systems like the ones I've mentioned.
> There's a huge amount of value in being able to copy JSON out of PHP and
> into e.g. CURL to make a query to ElasticSearch without worrying that I'v=
e
> accidentally nested one level too deep or shallow, or accidentally
> mistranslating my arrays into JSON.
>
> This is not about saving five characters every time I type array(), it's
> about making my systems all work together in a way that's a little less
> abstracted, and a lot less prone to error.
>
> S
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>

--90e6ba53b0707ffbc404a4bccb2b--