Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:52684
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.212.173 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=DP10shNsbaS7PMFPDIWaheS1VQbVfpfVfIUpSZrkiv8J2TIp0dwRmonN2DBOZYxo1B
         2b8YnSUdXDatIBMSE4AFeb31QQeWsWt16hh4y2VysS/MwkYBXaV/NfXvLGZJkz7Cf1EZ
         yoneJzc/YKk1z3MpPVlOP0u+235FDei874RTg=
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
In-Reply-To: <4DE66128.1080006@lerdorf.com>
Date: Wed, 1 Jun 2011 11:03:49 -0500
Cc: Justin Carmony <justin@justincarmony.com>,
 PHP internals <internals@lists.php.net>
Content-Transfer-Encoding: quoted-printable
Message-ID: <BB3E2E3A-17AD-4683-8891-395552818699@gmail.com>
References: <CA0AE764.2E07%marcel.esser@croscon.com> <BANLkTikzAz_GEdp_n042CfgNMrWWHjWb7g@mail.gmail.com> <BANLkTinfH4t=2V=LaRHKKX-NRa5KbpqAZA@mail.gmail.com> <BANLkTimAuOHDZmwAaZ8M6hkCGwhwYW4Baw@mail.gmail.com> <alpine.DEB.2.02.1106011234390.9040@whisky> <3C4EC449-1013-4ED6-9113-F37FAEBD0566@seancoates.com> <BANLkTimgVE9=QP1ixP4io6BU4WGqHLtHjg@mail.gmail.com> <94183529-D0B3-44B0-8AC8-CC229438F58D@roshambo.org> <CC516E66-FC9F-419B-AC13-8CAC9FD8BF94@justincarmony.com> <4DE66128.1080006@lerdorf.com>
To: Rasmus <rasmus@lerdorf.com>
Subject: Re: [PHP-DEV] Re: RFC: Short syntax for Arrays (redux)
From: shadda@gmail.com (Matt Wilson)

Would it be possible to have a vote on the various options being =
proposed here?

I think JSON syntax is definitely more concise and easier to type, as =
well as more convenient -- but I don't think it makes sense for PHP =
without changing how arrays work (I'm all for that, but that's a =
different discussion)

So for me, I'm -1 on a fudged JSON syntax with key: value syntax, even =
though I prefer that syntax over =3D>

But I'm =3D> on being able to simply drop 'array' from array =
delcarations.=20

I have a third option that I'm sure no one but me would like, what if we =
had some way to designate an item as an object, instead of an =
associative array? This could be handled either with : instead of =3D> =
or {} instead of (). {} instead of () seems to make more sense.

('arraykey' =3D> {'property': 'value'})

Mimicking JSON just seems pointless if we can't actually provide any =
benefit to doing so, since we'd still either have to differentiate =
between object/array *and* load via eval() (-) or json_decode() (+)

This RFC just seems premature, or at least doesn't offer enough voting =
options.

On Jun 1, 2011, at 10:56 AM, Rasmus wrote:

> On 06/01/2011 08:00 AM, Justin Carmony wrote:
>> In all seriousness, there is a vast majority of PHP developers who =
are not represented on this list. I was surprised to see someone =
mentioning for calling for another vote so soon after this discussion =
came up. Perhaps instead of debating on readability and usefulness, we =
actually do some research with major PHP users to get their opinions? =
I'm not saying we should have every PHP user in the world vote, but =
there are talented PHP developers who are not apart of the core that =
have valid and insightful views and opinions.
>>=20
>> So what I would first propose is we finalize the RFC because right =
now it is has two options, and doesn't deal with objects. I think =
everyone is starting to agree "=3D>" is much more uniform than ":", so =
lets drop the ":" from the RFC.=20
>>=20
>> Then, lets request some feedback from reputable PHP developers, like =
authors of popular frameworks and PHP solutions. This way we can get =
some real input from people who are not on the internals email list. =
This can help those who make the decision on whether or not to accept =
the RFC aware not only of their own personal opinion and preferences, =
but the opinions and preferences of the PHP community as a whole.
>>=20
>> I know I'm newer to the list, and don't want to step on any toes, but =
I think the RFC process could really benefit from getting this type of =
feedback.
>=20
> I think it is well understood that PHP internals discussion happens on
> this internals mailing list. It is not a restricted list in any way.
> Anybody is able to participate here if they want their voice heard.
>=20
> -Rasmus
>=20
> --=20
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>=20