Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:84435
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.171 as permitted sender)
Message-ID: <54FC5477.1040305@gmail.com>
Date: Sun, 08 Mar 2015 13:53:59 +0000
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: "internals@lists.php.net" <internals@lists.php.net>
References: <CAGa2bXai0cXrqeq3X2vTV8CjseAp=CUY29YaaxKniZENw0-x4g@mail.gmail.com> <op.xuxm3hojhuszwh@tsukapiou> <CAGa2bXbiQw82=+cGPurRwTnsD31MaZ9mM_e3WWLNPgcNz+H5zg@mail.gmail.com> <54F83061.60108@seld.be> <CAGa2bXaNcHvSAnLtFkUnLwWwYeXbrQptjqUPpOPBHXCc2_Vs6w@mail.gmail.com> <54FB44EE.6000704@gmail.com> <CAGa2bXZqw5LAHcBUQ7_Wkkh7BJHdM7ns4X3xTTkdEzLFy2Dt-g@mail.gmail.com> <6805F3C6-E73F-4A00-A94A-FE38B7E6D90F@gmail.com> <CAGa2bXYrvwAz2CCSmV4fN3LP2WUcCSS2eQtH_f92+Y-kjsQ3jg@mail.gmail.com>
In-Reply-To: <CAGa2bXYrvwAz2CCSmV4fN3LP2WUcCSS2eQtH_f92+Y-kjsQ3jg@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Re: [RFC] [DISCUSSION] Consistent Function Names
From: rowan.collins@gmail.com (Rowan Collins)

On 08/03/2015 01:25, Yasuo Ohgaki wrote:
> Hi Rowan,
>
> On Sun, Mar 8, 2015 at 8:31 AM, Rowan Collins <rowan.collins@gmail.com 
> <mailto:rowan.collins@gmail.com>> 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", as used by
>     is_callable() and function parameter typehints, and literally
>     everywhere that wants a callback. Since there's no such thing as a
>     function or method pointer, that definition includes a string
>     identifying a plain function, and two array forms, [string,
>     string] and [object, string], representing static and instance
>     methods, respectively. You can't not accept those forms as a
>     callback parameter in one particular function just to make things
>     tidier.
>
>
> I should have written "Let deprecate _all_ array callbacks" by 
> document and raise deprecate error in PHP7.
> Remove array callbacks in PHP 8.


In favour of what? We have no other way of telling a function expecting 
a callback to use an existing method.

And why? Because one particular function signature you want to create 
would be possible if "array" and "callback" were non-overlapping type 
hints? Is there something wrong with having a function that explicitly 
tells people it takes callbacks, rather than guessing based on the 
arguments you pass in?

Regards,

-- 
Rowan Collins
[IMSoP]