Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:52813
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain roshambo.org from 209.85.160.42 cause and error)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
In-Reply-To: <8377D924-763A-4C44-A018-052A74686BA9@seancoates.com>
Date: Thu, 2 Jun 2011 13:41:11 -0700
Cc: Pierre Joye <pierre.php@gmail.com>,
 PHP internals <internals@lists.php.net>
Content-Transfer-Encoding: quoted-printable
Message-ID: <9173A2D0-038A-493D-ACC5-2402416FAC79@roshambo.org>
References: <4DE5368A.6050603@moonspot.net> <BANLkTi=z+TLaLzKWArm7fmQ9h6syxGM8QA@mail.gmail.com> <0047B798-AFBC-41CF-A4EC-74A026B657FE@seancoates.com> <BANLkTimfjtDS3K=KE7WTRA6K+uxFR4Km4A@mail.gmail.com> <8377D924-763A-4C44-A018-052A74686BA9@seancoates.com>
To: Sean Coates <sean@seancoates.com>
Subject: Re: [PHP-DEV] RFC: Short syntax for Arrays (redux)
From: philip@roshambo.org (Philip Olson)


On Jun 2, 2011, at 1:19 PM, Sean Coates wrote:

>>> If people vote on this now, will further discussion about how this =
SHOULD
>>> work be shut down with "we already voted on this"?
>> which other discussions do you wish? Json is clearly not an option =
and
>> not enough people (but a couple) likes or wants it.
>>=20
>> The RFC is about short array syntax and as far as I can see there is
>> already a clear consensus for one of the proposed new syntax.
>=20
> I don't see why JSON (or JSON-like, or JavaScript Object Literal, or =
whatever the least politically-fired term of the moment) syntax is =
"clearly" not an option. I'm considering writing a new RFC that calls =
for first-class JSONishy syntax, but I have better things to do if it's =
already dead in the water.
>=20
> As much as I'd like to avoid drawing out this discussion, I think a =
premature vote that will be used as a political wedge to shut down all =
future syntaxes that don't use T_ARRAY is not in the best interest of =
PHP.

I share this concern, and it applies to future topics and discussions. I =
think you creating this RFC would be helpful, and that we as a group =
should respect the desired timeline for proposing this alternative RFC =
(I assume over the weekend?).

We won't be forgetting this topic (it feels like people are panicking =
like we will) so if said alternative isn't available or doesn't gain =
traction then the current [adjusted] RFC should be implemented.

Regards,
Philip