Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:85248
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.53 as permitted sender)
Message-ID: <550B5500.60004@gmail.com>
Date: Thu, 19 Mar 2015 23:00:16 +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: <54BEC072.5000507@mabe.berlin> <CAF+90c97pHH7+qnxV61RjTRv3-vOzHn9oGva3wHVGgbMEE=aSw@mail.gmail.com> <AAD87184-07B2-4E93-B872-1F2587CA9260@ajf.me> <54C28B63.1040506@gmail.com> <54C2E405.4090204@gmail.com> <A89BD51A-C383-4837-AADF-7FFED75374DC@gmail.com> <CAOWwgpmx8skuv4pQTkwft7E_TyjTgd9hsji5Or55Gx60_ucsnA@mail.gmail.com> <CAGa2bXZCpFYO41+wfd9nzqDV6jiBMEHnha1rprtEHa7mMBBD=A@mail.gmail.com> <CAOjCV8xo9hOAk8+zNXk1_V6BRP+kFkUgAasBQwgbzBGQvxxU3Q@mail.gmail.com> <CAGa2bXa+2Nozv0pe4yeGxD-wCALUaO9=46a7b=fkreocb3vn=g@mail.gmail.com> <550B49D8.4080608@gmail.com> <CAGa2bXapry36HbajH+4AiWBwy4RKKpkn9JL0bY=7WZD5hLZWNw@mail.gmail.com>
In-Reply-To: <CAGa2bXapry36HbajH+4AiWBwy4RKKpkn9JL0bY=7WZD5hLZWNw@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Inconsistencies in callable, call_user_func and direct
 variable calls
From: rowan.collins@gmail.com (Rowan Collins)

On 19/03/2015 22:43, Yasuo Ohgaki wrote:
> Hi Rowan,
>
> On Fri, Mar 20, 2015 at 7:12 AM, Rowan Collins 
> <rowan.collins@gmail.com <mailto:rowan.collins@gmail.com>> wrote:
>
>     On 19/03/2015 20:50, Yasuo Ohgaki wrote:
>
>         Hi Sebastian,
>
>         On Thu, Mar 19, 2015 at 9:48 PM, Sebastian B.-Hagensen
>         <sbj.ml.read@gmail.com <mailto:sbj.ml.read@gmail.com>
>         <mailto:sbj.ml.read@gmail.com <mailto:sbj.ml.read@gmail.com>>>
>         wrote:
>
>             2015-03-19 12:51 GMT+01:00 Yasuo Ohgaki
>         <yohgaki@ohgaki.net <mailto:yohgaki@ohgaki.net>
>             <mailto:yohgaki@ohgaki.net <mailto:yohgaki@ohgaki.net>>>:
>             > Distinguishing array and callable is problematic.
>             > Array callable is better to be deprecated in the long
>         run. IMHO.
>
>             Then how would you write an callback containing an already
>             constructed object?
>             $a = [$object, 'method'];
>
>             The alternative is unnecessarily cumbersome:
>             $a = function($methodArg1, $methodArg2) use($object) { return
>             $object->method($methodArg1, $methodArg2); };
>
>
>         I'm not proposing deprecate it soon, but in the long run.
>         It will need a decade to deprecate it.
>
>
>     It is not time that is needed, but an alternative way of
>     expressing "use this instance method as a callback", such as those
>     discussed elsewhere in the thread.
>
>
> I replied how it could be deprecated.
> I'm not commenting for it, but the deprecation discussion.
> You cannot restrict discussion to what you would want, can it?

I had no intention of restricting the discussion in any way, apologies 
if it came across that way.

Perhaps what I should have said is it is not *only* time that is needed 
- we need to design the replacement before it's worth even thinking 
about deprecating something.

Regards,

-- 
Rowan Collins
[IMSoP]