Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:53759
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: unknown (pb1.pair.com: domain php.net does not designate 91.184.32.3 as permitted sender)
Message-ID: <4E145FE2.5000001@php.net>
Date: Wed, 06 Jul 2011 15:15:14 +0200
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.17) Gecko/20110428 Fedora/3.1.10-1.fc15 Thunderbird/3.1.10
MIME-Version: 1.0
CC: internals@lists.php.net
References: <CABBJUpdt-gL49tZg3LfPO+rUc+_roJ=ApKPKebFJESim9BrH1Q@mail.gmail.com> <CADNQb0XcUYMmHRzaVLHt2oH4WBAwD5gMXHFMOV__UYHbE=AZ8w@mail.gmail.com>
In-Reply-To: <CADNQb0XcUYMmHRzaVLHt2oH4WBAwD5gMXHFMOV__UYHbE=AZ8w@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] [RFC] foreach_variable supporting T_LIST token
From: neufeind@php.net (Stefan Neufeind)

Hi,

On 07/06/2011 03:06 PM, Hannes Magnusson wrote:
> 2011/7/6 Xinchen Hui <laruence@gmail.com>:
>>
>>   T_LIST is not allowed to used with foreach before.
>>
>>   and then there comes a freature request:  #10203  allow
>> foreach($array as list($a,$b)
> 
> Ironically enough you managed to miss the last closing ), enforcing
> the point of this not being a natural syntax.
> 
> Furthermore, without reading the RFC, is this the same as
> foreach($array as $a => $b) {}

No, there $a would be the key. Intention would be, as I read the RFC,
that this could be an arbitrary list.

> or
> foreach($array as $e) {
> list($a, $b) = $e;
> }

Yes, I understood if like that. Just a short notation.

> or.. ?
> 
> that really doesn't look like something PHP should support imo.

Don't see too many bad things about the idea ...


Regards,
 Stefan