Re: Inconsistencies in callable, call_user_func and direct variable calls
| From: | Rowan Collins | Date: | Thu, 19 Mar 2015 22:12:40 +0000 |
| Subject: | Re: Inconsistencies in callable, call_user_func and direct variable calls | ||
| References: | 1 2 3 4 5 6 7 8 9 10 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-85245@lists.php.net to get a copy of this message | ||
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>> wrote: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. Regards, -- Rowan Collins [IMSoP]2015-03-19 12:51 GMT+01:00 Yasuo Ohgaki <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.