Re: re: removing an item from an array

Hi, I see why with new Criticism section in the wiki page. You've also misunderstood that array_udelete() is array_walk() variant, not array_filter(). This may be the good reason why we should have array_udelete :) Regards, -- Yasuo Ohgaki yohgaki@ohgaki.net 2012/8/22 Yasuo Ohgaki <yohgaki@ohgaki.net>: > 2012/8/22 Levi Morrison <morrison.levi@gmail.com>: >> On Tue, Aug 21, 2012 at 3:45 PM, Andrew Faulds <ajf@ajf.me> wrote: >>> On 21/08/12 22:43, Levi Morrison wrote: >>>> >>>> There is a reason to have a callable provided: custom comparison. >>>> Other array functions solve this by providing a u >>>> alternative: >>>> >>>> int array_udelete(&$array, $value, bool function($value, >>>> $key)) >>>> >>>> Let's not deviate from established array naming conventions. (Yasuo, >>>> I'm looking at you) >>>> >>>> Cheers, >>>> >>>> Levi Morrison >>> >>> Yeah, this looks like a good solution and we have the best of both worlds. >>> >>> We get int array_delete(&$array, $value, $strict=TRUE); and int >>> array_udelete(&$array, $value, $callback=bool function ($value $key)); >>> >>> :) >>> >>> >> >> I'll still vote no on the RFC if it ever comes to it :) >> >> I'm only contributing here because I don't want pure madness to ever >> come to a vote when I'm absent and get voted in . . . > > Just curious why? > > Regards, > > -- > Yasuo Ohgaki > yohgaki@ohgaki.net