On 1/11/2013 11:53 PM, Anthony Ferrara wrote:
From what I can see this new function doesn't fit any of those three to a
significant enough extent. All three are definitely subjective, but I'm
leaning towards a no vote because I just don't feel there's enough
justification for the new function when weighted against the bloat factor...
My $0.02... Thoughts?
Anthony
I can see a use-case for this but the PDO relationship is a poor reason
for having it. The whole PDO thing threw me off such that I was in the
same boat as Anthony with the same thoughts. Contrived examples aren't
helpful for passing a RFC. Here is a more reasonable example:
echo implode(", ", array_column($myarray, 2));
It saves constructing a separate array or writing my own function in PHP
userland that comes with the risk of naming conflicts. array_column()
is a handy shortcut to a process. I've not thought about writing a PHP
userland function for this before because it generally only takes a
couple of lines of code. This formalizes that process and simplifies code.
It isn't a function I'll necessarily use every day, but the above
example is more useful and will speak to more developers than the PDO
example will.
I have a separate recommendation that could eliminate the need for the
third optional parameter of array_column(), but I'll start another
thread on this list for it.
--
Thomas Hruska
CubicleSoft President
I've got great, time saving software that you might find useful.
http://cubiclesoft.com/
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
