On 06/22/2012 04:20 PM, Scott MacVicar wrote:
Hey Ben,
On 22 Jun 2012, at 08:52, Ben Ramsey wrote:
On 6/22/12 5:32 AM, Léo Peltier wrote:
Hi,
Shouldn't this be called 'array_pluck'?
This is the name people usually use when implementing it in PHP (see
"array_pluck(" vs "array_column(" in Goog
Hey Ben,
On 22 Jun 2012, at 08:52, Ben Ramsey wrote:
> On 6/22/12 5:32 AM, Léo Peltier wrote:
>> Hi,
>>
>> Shouldn't this be called 'array_pluck'?
>> This is the name people usually use when implementing it in PHP (see
>> "array_pluck(" vs "array_column(" in Google) or in other languages/libs
>>
On Fri, Jun 22, 2012 at 11:52 AM, Ben Ramsey wrote:
> On 6/22/12 5:32 AM, Léo Peltier wrote:
>
>> Hi,
>>
>> Shouldn't this be called 'array_pluck'?
>> This is the name people usually use when implementing it in PHP (see
>> "array_pluck(" vs "array_column(" in Google) or in other languages/libs
>>
I've made several changes to accommodate several issues raised on this
list. See
https://github.com/cataphract/php-src/compare/break_iterator
All but the first two commits are new. Please see the test cases for
doubts concerning usage.
--
Gustavo Lopes
--
PHP Internals - PHP Runtime Devel
Hi Ben,
I've tested your patch on Windows, it compiles and the tests pass. All the
best with that :)
Regards
Anatoliy
Am Fr, 22.06.2012, 17:52 schrieb Ben Ramsey:
> On 6/22/12 5:32 AM, Léo Peltier wrote:
>> Hi,
>>
>> Shouldn't this be called 'array_pluck'?
>> This is the name people usually use
On Fri, Jun 22, 2012 at 6:25 PM, Laruence wrote:
> Hi internalers:
>
> there comes a FR, #62343 https://bugs.php.net/bug.php?id=62343
>
> the bug self is about class alias, but it also metioned a new
> parameter $user_only to get_declared_classes.
>
> the FR makes sense to me, for
Hi internalers:
there comes a FR, #62343 https://bugs.php.net/bug.php?id=62343
the bug self is about class alias, but it also metioned a new
parameter $user_only to get_declared_classes.
the FR makes sense to me, for now, get_defined_functions 's
return will points which fun
On 6/22/12 5:32 AM, Léo Peltier wrote:
Hi,
Shouldn't this be called 'array_pluck'?
This is the name people usually use when implementing it in PHP (see
"array_pluck(" vs "array_column(" in Google) or in other languages/libs
(see underscorejs, prototypejs and RoR).
I'm open to changing or alia
Hi,
Shouldn't this be called 'array_pluck'?
This is the name people usually use when implementing it in PHP (see
"array_pluck(" vs "array_column(" in Google) or in other languages/libs (see
underscorejs, prototypejs and RoR).
--
Léo Peltier
--
PHP Internals - PHP Runtime Development Mailin
On Thu, 2012-06-21 at 22:35 -0400, Anthony Ferrara wrote:
> Actually, the more I think about it, this would result in an
> inadvertent API change. Right now, if you have a SQL syntax error, the
> error would be thrown by ->execute(). But with this change, the error
> would be thrown by ->prepare().
Hi,
>> In addition to == operator, >, <, >=, and <= operators are influenced.
>>
>> And, hexdecimal format for big number is now case-sensitive.
>>
>> http://www.mail-archive.com/internals@lists.php.net/msg58789.html
>
> Can you add some phpt tests for all the cases you've raised?
This is the php
11 matches
Mail list logo
