Re: [PHP-DEV] Re: [RFC] [DISCUSSION] Consistent Function Names

2015-03-08 Thread Rowan Collins
On 08/03/2015 01:25, Yasuo Ohgaki wrote: Hi Rowan, On Sun, Mar 8, 2015 at 8:31 AM, Rowan Collins > wrote: What? That's not the same thing at all. I'm pretty sure those functions are deprecated *because* we have array callback forms, so you can use ca

Re: [PHP-DEV] Re: [RFC] [DISCUSSION] Consistent Function Names

2015-03-07 Thread Yasuo Ohgaki
Hi Rowan, On Sun, Mar 8, 2015 at 8:31 AM, Rowan Collins wrote: > What? That's not the same thing at all. I'm pretty sure those functions > are deprecated *because* we have array callback forms, so you can use > call_user_func to call a method. > > PHP has a well-defined definition of "callable",

Re: [PHP-DEV] Re: [RFC] [DISCUSSION] Consistent Function Names

2015-03-07 Thread Rowan Collins
On 7 March 2015 22:47:48 GMT, Yasuo Ohgaki wrote: >Hi Rowan, > >On Sun, Mar 8, 2015 at 3:35 AM, Rowan Collins >wrote: > >> On 06/03/2015 23:03, Yasuo Ohgaki wrote: >> >>> We have a lot of array_u*() functions such as >>> >>> http://php.net/manual/en/function.array-uintersect-uassoc.php >>> array

Re: [PHP-DEV] Re: [RFC] [DISCUSSION] Consistent Function Names

2015-03-07 Thread Yasuo Ohgaki
Hi Rowan, On Sun, Mar 8, 2015 at 3:35 AM, Rowan Collins wrote: > On 06/03/2015 23:03, Yasuo Ohgaki wrote: > >> We have a lot of array_u*() functions such as >> >> http://php.net/manual/en/function.array-uintersect-uassoc.php >> array array_uintersect_uassoc ( array $array1 , array $array2 [, arr

Re: [PHP-DEV] Re: [RFC] [DISCUSSION] Consistent Function Names

2015-03-07 Thread Yasuo Ohgaki
Hi all, On Sat, Mar 7, 2015 at 7:32 PM, Lester Caine wrote: > On 06/03/15 23:18, Yasuo Ohgaki wrote: > > Hi Lester, > > > > On Thu, Mar 5, 2015 at 8:46 PM, Lester Caine wrote: > > > >> On 05/03/15 09:40, Rowan Collins wrote: > > > > Good point! > > I'll update documents so that main

Re: [PHP-DEV] Re: [RFC] [DISCUSSION] Consistent Function Names

2015-03-07 Thread Rowan Collins
On 06/03/2015 23:03, Yasuo Ohgaki wrote: We have a lot of array_u*() functions such as http://php.net/manual/en/function.array-uintersect-uassoc.php array array_uintersect_uassoc ( array $array1 , array $array2 [, array $... ], callable $value_compare_func , callable $key_compare_func ) this can

Re: [PHP-DEV] Re: [RFC] [DISCUSSION] Consistent Function Names

2015-03-07 Thread Lester Caine
On 06/03/15 23:18, Yasuo Ohgaki wrote: > Hi Lester, > > On Thu, Mar 5, 2015 at 8:46 PM, Lester Caine wrote: > >> On 05/03/15 09:40, Rowan Collins wrote: > > Good point! > I'll update documents so that main function is prefered name/function > to be > used. >>> This would be f

Re: [PHP-DEV] Re: [RFC] [DISCUSSION] Consistent Function Names

2015-03-06 Thread Yasuo Ohgaki
Hi Lester, On Thu, Mar 5, 2015 at 8:46 PM, Lester Caine wrote: > On 05/03/15 09:40, Rowan Collins wrote: > >> > > >> >Good point! > >> >I'll update documents so that main function is prefered name/function > >> >to be > >> >used. > > This would be fine if all the users read the manual, and only

Re: [PHP-DEV] Re: [RFC] [DISCUSSION] Consistent Function Names

2015-03-06 Thread Yasuo Ohgaki
Hi Jordi, On Thu, Mar 5, 2015 at 7:30 PM, Jordi Boggiano wrote: > On 05/03/2015 08:07, Yasuo Ohgaki wrote: > >> So array functions are subject to be changed. >> >> bool in_array ( mixed $needle , array $haystack [, bool $strict ] ) >> Renamed to array_in() and fix order. >> >> mixed array_se

Re: [PHP-DEV] Re: [RFC] [DISCUSSION] Consistent Function Names

2015-03-05 Thread Lester Caine
On 05/03/15 09:40, Rowan Collins wrote: >> > >> >Good point! >> >I'll update documents so that main function is prefered name/function >> >to be >> >used. > This would be fine if all the users read the manual, and only the manual. > What about the thousands of books, tutorials, blog posts, Stack O

Re: [PHP-DEV] Re: [RFC] [DISCUSSION] Consistent Function Names

2015-03-05 Thread Jordi Boggiano
On 05/03/2015 08:07, Yasuo Ohgaki wrote: So array functions are subject to be changed. bool in_array ( mixed $needle , array $haystack [, bool $strict ] ) Renamed to array_in() and fix order. mixed array_search ( mixed $needle , array $haystack [, bool $strict ] ) Renamed to array_find(

Re: [PHP-DEV] Re: [RFC] [DISCUSSION] Consistent Function Names

2015-03-05 Thread Rowan Collins
On 5 March 2015 08:50:12 GMT, Yasuo Ohgaki wrote: >Hi Niklas, > >On Thu, Mar 5, 2015 at 5:29 PM, Niklas Keller wrote: > >> If we introduce those new aliases, it should be clearly stated in the >docs >> which function should be used, maybe we can remove the old one in the >far >> future then. But

Re: [PHP-DEV] Re: [RFC] [DISCUSSION] Consistent Function Names

2015-03-05 Thread Yasuo Ohgaki
Hi Niklas, On Thu, Mar 5, 2015 at 5:29 PM, Niklas Keller wrote: > If we introduce those new aliases, it should be clearly stated in the docs > which function should be used, maybe we can remove the old one in the far > future then. But the more important point is, that it's not that confusing >

Re: [PHP-DEV] Re: [RFC] [DISCUSSION] Consistent Function Names

2015-03-05 Thread Niklas Keller
If we introduce those new aliases, it should be clearly stated in the docs which function should be used, maybe we can remove the old one in the far future then. But the more important point is, that it's not that confusing to users. Which one should I use? Why's there another one? We already have

Re: [PHP-DEV] Re: [RFC] [DISCUSSION] Consistent Function Names

2015-03-05 Thread Yasuo Ohgaki
Hi Benoit, On Wed, Mar 4, 2015 at 2:34 AM, Benoit Schildknecht wrote: > I think the new functions must have consistent parameters order too. I > think it is about the right time, so we'll have a cleaner and more logical > language. > > ATM, it's a real headache, we constantly have to read the do

[PHP-DEV] Re: [RFC] [DISCUSSION] Consistent Function Names

2015-03-03 Thread Benoit Schildknecht
Hi, I think the new functions must have consistent parameters order too. I think it is about the right time, so we'll have a cleaner and more logical language. ATM, it's a real headache, we constantly have to read the documentation to make sure we give the arguments in the right order.