Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:90695
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain lsces.co.uk from 217.147.176.204 cause and error)
To: internals@lists.php.net
References: <3B.E6.32157.D3DFA965@pb1.pair.com> <569C91FE.8030605@php.net>
Message-ID: <569CDC1C.2070304@lsces.co.uk>
Date: Mon, 18 Jan 2016 12:35:40 +0000
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101
 Thunderbird/38.5.0
MIME-Version: 1.0
In-Reply-To: <569C91FE.8030605@php.net>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] [RFC] Allow specifying keys in list()
From: lester@lsces.co.uk (Lester Caine)

On 18/01/16 07:19, Michael Wallner wrote:
>> Here's an RFC that would extend the syntax of list() to be more useful
>> > with associative arrays:
>> > 
>> > https://wiki.php.net/rfc/list_keys
>> > 
>> > Please read it and tell me your thoughts.
> Hi!
> 
> I found the idea convincing from the first read, but maybe it's just my
> mind's assumptions about list() that I dislike the resulting syntax,
> yet, it seems to be the logical choice.
> 
> So, maybe I'm just trying to say, that I don't like list() to be reused
> for that, but I don't have any better idea otherwise.

As someone still using 'extract' in legacy code, I can sort of see the
logistics of this, but why not just extend 'extract' to use the current
object rather than the symbol table. It already has handling for
duplicate keys and to prefix the 'array' name to the resulting variables.

-- 
Lester Caine - G8HFL
-----------------------------
Contact - http://lsces.co.uk/wiki/?page=contact
L.S.Caine Electronic Services - http://lsces.co.uk
EnquirySolve - http://enquirysolve.com/
Model Engineers Digital Workshop - http://medw.co.uk
Rainbow Digital Media - http://rainbowdigitalmedia.co.uk