Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:64886 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 41478 invoked from network); 12 Jan 2013 15:35:07 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 12 Jan 2013 15:35:07 -0000 X-Host-Fingerprint: 68.52.111.150 c-68-52-111-150.hsd1.tn.comcast.net Received: from [68.52.111.150] ([68.52.111.150:2248] helo=localhost.localdomain) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 9A/82-24230-BA281F05 for ; Sat, 12 Jan 2013 10:35:07 -0500 Message-ID: <9A.82.24230.BA281F05@pb1.pair.com> To: internals@lists.php.net Date: Sat, 12 Jan 2013 09:34:55 -0600 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:13.0) Gecko/20120614 Thunderbird/13.0.1 MIME-Version: 1.0 References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Posted-By: 68.52.111.150 Subject: Re: [PHP-DEV] [VOTE] array_column() function From: ramsey@php.net (Ben Ramsey) On 1/12/13 9:19 AM, Derick Rethans wrote: > I'm liking this, why start with an function alias already when > introducing a new feature? I figured this would be a frequent question, and I was right. :-) In earlier discussions (June 2012), when I first introduced array_column(), much of the discussion revolved around the name and not the functionality. I agreed with arguments for array_column() and arguments for array_pluck(), so I added an alias. Here's why I think the alias should be considered: 1) Userland PHP developers instantly recognize array_column(). It's self-descriptive, and they know what it means. 2) Developers coming from other languages (Ruby, JavaScript, etc.) will instantly recognize array_pluck(). It's what they'll be looking for to do the same thing, but they won't be looking for array_column(). -Ben