Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:90697
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.45 as permitted sender)
To: internals@lists.php.net
References: <3B.E6.32157.D3DFA965@pb1.pair.com> <569C91FE.8030605@php.net>
 <569CDC1C.2070304@lsces.co.uk>
Message-ID: <569CDF94.9070500@gmail.com>
Date: Mon, 18 Jan 2016 12:50:28 +0000
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101
 Thunderbird/38.5.1
MIME-Version: 1.0
In-Reply-To: <569CDC1C.2070304@lsces.co.uk>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] [RFC] Allow specifying keys in list()
From: rowan.collins@gmail.com (Rowan Collins)

Lester Caine wrote on 18/01/2016 12:35:
> 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.

The main advantage I can see is that this is a whitelist-based approach 
- you state explicitly in your code what you expect the array to look 
like, and what variables you are assigning based on it. This is very 
different from "whatever's in this array, turn it into a variable".

The "current object" was just one possible use case, have a look at some 
of the other examples in the RFC, such as:

list(
     CURLOPT_GET => $isGet,
     CURLOPT_POST => $isPost,
     CURLOPT_URL => $url
) = $curlOptions;

Note that $curlOptions probably had other things in it, $url may be an 
existing variable getting a new value. The best extract would give you 
is $curloption_10002, which isn't all that useful.

Regards,
-- 
Rowan Collins
[IMSoP]