[VOTE]Call for voting: support use list in foreach View as Markdown

Hi:
This feature introduces list() support in foreach constructs(more
info can be found here: https://wiki.php.net/rfc/foreachlist).

please vote for this: https://wiki.php.net/rfc/foreachlist#vote

Hi Lauruence!

Is this vote just for list() or also for error suppression? I'd vote
+1 on the first, but -1 on the second, so it would be nice to make it
more clear ;)
Hi,

okey, I opened another vote for the foreach list with silent token
supporting.

thanks

Nikita

Sorry, I feel like I missed the discussion phase of this RFC. I'm
unclear about how this behavior in the construct will affect existing
code. Currently, you can only use list() with arrays that have
sequential numeric keys starting from 0. So the follow does not
currently work with the list construct...

list($x, $y) = array('x'=>1, 'y'=>2); // This won't work

/* This won't work either.. at least not the way I'd expect because $y
will end up being 1 and $x will be null and an E_NOTICE level error is
thrown. /
list($x, $y) = array(1=>1, 2=>2);
var_dump($x, $y);
/
NULL
int(1)
*/

While I see the use of the list construct as a minor improvement in
readability (it does add some syntactic sugar), I also can't imagine
that it makes things any more consistent, which is one of the points
of this RFC.

This also means that if we chose to avoid this extra level of
indirection by way of list in foreach constructs we can't expect to
access the key, which might make for another ambiguity and lead us
back to just using something like the following...

$array = array(
'Cape Cod' => array('lat' => 12.20, 'long' => 34.60),
'North Shore' => array('lat' => 18.72, 'long' => 4.11),
'Mount Erie' => array('lat' => 6.02, 'long' => 21.79),
);
foreach ($array as $point => $coordinates) {
$lat = $coordinates['lat'];
$long = $coordinates['long'];
echo "Coordinates for $point are: LAT = $lat, LONG = $long\n";
}

I understand we can simply say this would not be an ideal use case for
this, but then it becomes a tiny variation in syntax that only solves
a specific problem.

On Sun, Aug 26, 2012 at 8:42 PM, Stas Malyshev smalyshev@sugarcrm.comwrote:

Hi!

foreach supports list syntax: 11 for yes, 4 for no. accepted.
foreach supports list with silent token: 2 for yes, 10 for no.
denied.

And here's again the problem with this voting setup. With all these long
discussions about people not getting votes we have 15 people that
bothered to vote at all, and essentially the vote is decided by one or
two single votes, and the vote doesn't even have to be from a PHP
contributor - but the vote of anybody who can register on PHP wiki is
enough to decide questions on the core of the language. And I'm not
talking about "the voice of the masses" there but by a single vote of
anybody who bothers to vote, which 99% of people just do not.

I do not this it is a healthy state of things. Sorry to raise the topic
that was discussed 1000 times before, but the situation does not seem to
improve.

Stanislav Malyshev, Software Architect
SugarCRM: http://www.sugarcrm.com/
(408)454-6900 ext. 227

--

I got a PHP Wiki account but couldn't vote. Are you sure the Wiki accounts
got the permissions to vote?

Hi!

foreach supports list syntax: 11 for yes, 4 for no. accepted.
foreach supports list with silent token: 2 for yes, 10 for no. denied.

And here's again the problem with this voting setup. With all these long
discussions about people not getting votes we have 15 people that
bothered to vote at all, and essentially the vote is decided by one or
two single votes, and the vote doesn't even have to be from a PHP
contributor - but the vote of anybody who can register on PHP wiki is
enough to decide questions on the core of the language. And I'm not
talking about "the voice of the masses" there but by a single vote of
anybody who bothers to vote, which 99% of people just do not.

Only people with a VCS account (or voting group) can vote.

Nikita

Hi:
sorry to replying top.

this is really a minor features, so few people are interesting in

this. thus fewer people will vote for it.

if people interesting in the RFC, he will vote. so I think it's okey..

thanks

Hi!

foreach supports list syntax: 11 for yes, 4 for no. accepted.
foreach supports list with silent token: 2 for yes, 10 for no. denied.

And here's again the problem with this voting setup. With all these long
discussions about people not getting votes we have 15 people that
bothered to vote at all, and essentially the vote is decided by one or
two single votes, and the vote doesn't even have to be from a PHP
contributor - but the vote of anybody who can register on PHP wiki is
enough to decide questions on the core of the language. And I'm not
talking about "the voice of the masses" there but by a single vote of
anybody who bothers to vote, which 99% of people just do not.

I do not this it is a healthy state of things. Sorry to raise the topic
that was discussed 1000 times before, but the situation does not seem to
improve.

Stanislav Malyshev, Software Architect
SugarCRM: http://www.sugarcrm.com/
(408)454-6900 ext. 227

--
Laruence Xinchen Hui
http://www.laruence.com/

Hi!

foreach supports list syntax: 11 for yes, 4 for no. accepted.
foreach supports list with silent token: 2 for yes, 10 for no. denied.

And here's again the problem with this voting setup. With all these long
discussions about people not getting votes we have 15 people that
bothered to vote at all, and essentially the vote is decided by one or
two single votes, and the vote doesn't even have to be from a PHP
contributor - but the vote of anybody who can register on PHP wiki is
enough to decide questions

No. One has to get the vote/rfc karma. If that has changed, we have
you restore this restriction.

anybody who bothers to vote, which 99% of people just do not.

If one does not participate, his fault.

Btw, we also have the 2/3 rule for language change as well.

Cheers,
Pierre