Re: Inconsistencies in callable, call_user_func and direct variable calls

From: Date: Tue, 20 Jan 2015 21:46:18 +0000
Subject: Re: Inconsistencies in callable, call_user_func and direct variable calls
References: 1  Groups: php.internals 
Request: Send a blank email to [email protected] to get a copy of this message
On Tue, Jan 20, 2015 at 9:54 PM, Marc Bennewitz <[email protected]> wrote:

> valid for call_user_func[_array] and callable type-hint but invalid for
> for direct variable calls:
> - string "MyClass::staticFunc"
> - string "self::staticFunc"
> - string "static::staticFunc"
> - string "parent::func"
> - string "parent::staticFunc"
>
> see http://3v4l.org/1oSO3
>
> Thoughts ?
>

I would prefer deprecating this alternative notation instead of adding more
support for it. The [$class, $method] form is the canonical form we support
everywhere and which is consistent with the [$obj, $method] callbacks.
There's no point supporting another alternative notation, especially if it
was effectively unusable for a while now already.

Nikita


Thread (32 messages)

« previous php.internals (#80906) next »