Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:64916 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 31944 invoked from network); 13 Jan 2013 00:38:48 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 13 Jan 2013 00:38:48 -0000 Authentication-Results: pb1.pair.com smtp.mail=ww.galen@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=ww.galen@gmail.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.212.180 as permitted sender) X-PHP-List-Original-Sender: ww.galen@gmail.com X-Host-Fingerprint: 209.85.212.180 mail-wi0-f180.google.com Received: from [209.85.212.180] ([209.85.212.180:46937] helo=mail-wi0-f180.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 59/71-24212-61202F05 for ; Sat, 12 Jan 2013 19:38:47 -0500 Received: by mail-wi0-f180.google.com with SMTP id hj13so563022wib.13 for ; Sat, 12 Jan 2013 16:38:44 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to:content-type; bh=bKL6RcnSWhqj9jttKXarJ3/XRsygGhY6FF6bom1KNyA=; b=kiMqB/wRCwTf9IbwWajsySf/eEMKnRSMaiEeXfSMDyNyYplBIJsn9trdMTS0Wz6yox 24EfUHJjdcoTB4nwiKoF51z1bcCS5UFwQnqxtVirIWLj1E0lr5cdQbOTjkXN9qazCuhZ 0X3XYF/PkLr2EYgzGm9X2Rk8zFuy9jl5Ndb6iVSl5x+tHeOkmxv623EISJcfxVzJ0/fj qm1zgBQTdj5RuLc3qXM1pcLAwFVOMv6hBQjOPWRbIKV0VubTpKL5bbriW/0eDQ6dphQr yxJlzga0HM7SyV75ZmTSaCzU2atP+7PW/XzE6ffshkx8ckzG7PlkvNtSsbTPTpC6VekM RJ/Q== X-Received: by 10.180.79.37 with SMTP id g5mr5853710wix.8.1358037524310; Sat, 12 Jan 2013 16:38:44 -0800 (PST) MIME-Version: 1.0 Received: by 10.217.39.193 with HTTP; Sat, 12 Jan 2013 16:38:04 -0800 (PST) In-Reply-To: <9A.82.24230.BA281F05@pb1.pair.com> References: <9A.82.24230.BA281F05@pb1.pair.com> Date: Sat, 12 Jan 2013 16:38:04 -0800 Message-ID: To: "internals@lists.php.net" Content-Type: multipart/alternative; boundary=f46d044306b03a6c7504d320c0ed Subject: Re: [PHP-DEV] [VOTE] array_column() function From: ww.galen@gmail.com (Galen Wright-Watson) --f46d044306b03a6c7504d320c0ed Content-Type: text/plain; charset=ISO-8859-1 On Sat, Jan 12, 2013 at 7:34 AM, Ben Ramsey wrote: > 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(). > As an alternative to an alias, what about a manual page for whichever name isn't used that redirects or (like delete ) refers to the one that is used? Of course, this wouldn't help when someone is searching or browsing through code. For #2, were you envisioning the developer looking for a "pluck" function in the manual, browsing source and coming across the function, searching (grep &c) the code for a "pluck" function, or something else? --f46d044306b03a6c7504d320c0ed--