Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:80906
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.179 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <54BEC072.5000507@mabe.berlin>
References: <54BEC072.5000507@mabe.berlin>
Date: Tue, 20 Jan 2015 22:46:18 +0100
Message-ID: <CAF+90c97pHH7+qnxV61RjTRv3-vOzHn9oGva3wHVGgbMEE=aSw@mail.gmail.com>
To: Marc Bennewitz <dev@mabe.berlin>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=001a11c26a3a741600050d1c5eb7
Subject: Re: [PHP-DEV] Inconsistencies in callable, call_user_func and direct
 variable calls
From: nikita.ppv@gmail.com (Nikita Popov)

--001a11c26a3a741600050d1c5eb7
Content-Type: text/plain; charset=UTF-8

On Tue, Jan 20, 2015 at 9:54 PM, Marc Bennewitz <dev@mabe.berlin> 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

--001a11c26a3a741600050d1c5eb7--