Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:90718
Return-Path: <ajf@ajf.me>
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 3555 invoked from network); 19 Jan 2016 18:04:06 -0000
Received: from unknown (HELO lists.php.net) (127.0.0.1)
  by localhost with SMTP; 19 Jan 2016 18:04:06 -0000
X-Host-Fingerprint: 178.62.40.5 ajf.me  
Received: from [178.62.40.5] ([178.62.40.5:5518] helo=localhost.localdomain)
	by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP
	id 39/90-32754-59A7E965 for <internals@lists.php.net>; Tue, 19 Jan 2016 13:04:05 -0500
Message-ID: <39.90.32754.59A7E965@pb1.pair.com>
To: internals@lists.php.net
References: <3B.E6.32157.D3DFA965@pb1.pair.com>
Date: Tue, 19 Jan 2016 18:04:01 +0000
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:42.0)
 Gecko/20100101 Firefox/42.0 SeaMonkey/2.39
MIME-Version: 1.0
In-Reply-To: <3B.E6.32157.D3DFA965@pb1.pair.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Posted-By: 178.62.40.5
Subject: Re: [RFC] Allow specifying keys in list()
From: ajf@ajf.me (Andrea Faulds)

Hi again,

I've updated the RFC to v1.1, because I've resolved the open issue of 
whether to allow arbitrary expressions for keys. It seems that the risk 
of confusion was less than I thought it was, and allowing anything not 
only simplifies implementation, but means you can do things like have 
object keys (when working with SplObjectStorage, for example).

You may wish to look over the RFC again: https://wiki.php.net/rfc/list_keys

Thanks.

-- 
Andrea Faulds
https://ajf.me/