Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:64961 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 72825 invoked from network); 14 Jan 2013 23:55:09 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 14 Jan 2013 23:55:09 -0000 Authentication-Results: pb1.pair.com smtp.mail=mjpelmear@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=mjpelmear@gmail.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.160.51 as permitted sender) X-PHP-List-Original-Sender: mjpelmear@gmail.com X-Host-Fingerprint: 209.85.160.51 mail-pb0-f51.google.com Received: from [209.85.160.51] ([209.85.160.51:42500] helo=mail-pb0-f51.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id A3/8E-22727-DDA94F05 for ; Mon, 14 Jan 2013 18:55:09 -0500 Received: by mail-pb0-f51.google.com with SMTP id ro12so2460357pbb.10 for ; Mon, 14 Jan 2013 15:55:06 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=tPie1nxki0/24WhFEiV7Ghm5xbIJt1iHxsPRtbetSQo=; b=K/G90GvJmq9SgGV/7CbP+Z/K3BYXkxhz53UArV7+kUmXmw3y++YQTMrfHQOWwiAO+E xcmluUrFS++3gxbtgzaXLTdUY3a4KIzi+CMh8+XwOacHCRRsX3rVjWuEiHqRr2/9gW74 2kU2nXEiqY1Jmn2iy43o/aAtdXooGb2j7x2y9PxCRneVbzosRC/L6B+kMVuch5anKu5Y HsbLc30txN6VgH1jipA8pzlY/Ar9lz046T1Zuz501D6sbASwg+pdpgBa46XX9t1S77Jw 9neXhODEksRPkN6wyI0D+rp/W7YFr17/+hz2jIFQui4Gs0jnHA7WiGxb7H/E8kJBu/Sw 0iLg== X-Received: by 10.69.0.40 with SMTP id av8mr260351780pbd.117.1358207706779; Mon, 14 Jan 2013 15:55:06 -0800 (PST) Received: from [192.168.1.123] (cpe-98-154-250-197.socal.res.rr.com. [98.154.250.197]) by mx.google.com with ESMTPS id ov4sm9006663pbb.45.2013.01.14.15.55.04 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 14 Jan 2013 15:55:05 -0800 (PST) Message-ID: <50F49AD7.70409@gmail.com> Date: Mon, 14 Jan 2013 15:55:03 -0800 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:14.0) Gecko/20120714 Thunderbird/14.0 MIME-Version: 1.0 To: internals@lists.php.net References: <50F4802C.5070003@php.net> <42E0BBCF-074E-493C-9FEA-CE87EE21CE7D@strojny.net> In-Reply-To: <42E0BBCF-074E-493C-9FEA-CE87EE21CE7D@strojny.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] [VOTE] array_column() function From: mjpelmear@gmail.com (Matt Pelmear) On 01/14/2013 02:19 PM, Lars Strojny wrote: > Hi Ben, > > Am 14.01.2013 um 23:16 schrieb Pierre Joye : > [...] >> Up to you, but I'd to suggest again to re do the vote and add the >> naming option, easy, clear, open. > I was one of the people changing from yes to no because of the name. I like the functionality but I prefer no new array function over one with yet another strange name. > > cu, > Lars You'd rather the new method misuse the meaning of the word "pluck" over following an established convention within it's own environment that is meaningful? If it is called "array_pluck" it should remove the data in question from the original array. (I'm not saying that is a desirable feature here, I'm just saying that makes more sense based on the meaning of the name you seem to prefer.) If there's a problem with the array functions not being verbs (which, personally, I don't think is a huge issue as long as it is consistent), that should be addressed for the array functions as an entire set-- not for one particular one. Re: the vote: There is no point in redoing the vote at this point. If the vote does not pass as it is, that means either the community doesn't support the new feature or they don't support the proposed function name. It's obvious, based on the current vote results, that the community does support the feature, so it is simply a matter of issuing a second vote if this one fails. -Matt