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 =>
But I'm => on being able to simply drop 'array' from array delcarations.
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 => or {} instead of (). {}
instead of () seems to make more sense.
('arraykey' => {'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.
>>
>> 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 "=>" is much more uniform than ":", so lets drop the ":" from the
>> RFC.
>>
>> 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.
>>
>> 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.
>
> 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.
>
> -Rasmus
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
