Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:80903
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.214.180 as permitted sender)
MIME-Version: 1.0
Sender: morrison.levi@gmail.com
In-Reply-To: <CADajX4AX0ZgHRmUvXWjkUkXLbBcvKmopY+T+dozE-M08asQojQ@mail.gmail.com>
References: <54BEC072.5000507@mabe.berlin>
	<CADajX4AX0ZgHRmUvXWjkUkXLbBcvKmopY+T+dozE-M08asQojQ@mail.gmail.com>
Date: Tue, 20 Jan 2015 14:20:56 -0700
Message-ID: <CAFMT4NoB_=UYpg_cWSa4uExPXUw18x3dQ3iaSNwc73Dz29Knjw@mail.gmail.com>
To: Adam Harvey <aharvey@php.net>
Cc: Marc Bennewitz <dev@mabe.berlin>, PHP internals <internals@lists.php.net>, 
	julien pauli <jpauli@php.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] Inconsistencies in callable, call_user_func and direct
 variable calls
From: levim@php.net (Levi Morrison)

On Tue, Jan 20, 2015 at 1:59 PM, Adam Harvey <aharvey@php.net> wrote:
> On 20 January 2015 at 12:54, 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 ?
>
> This is https://bugs.php.net/bug.php?id=3D68475 =E2=80=94 Julien and I bo=
th have
> PoC branches implementing this, and agree that it should be fixed in
> PHP 7, although I think we differ on whether an RFC is required or
> not.

If `is_callable($f)` returns `true` then it's a bug if you can't call
it with `$f(...$args)`. That's my opinion anyway. I was actually made
aware of this bug some time ago but whenever I intended to fix it I
couldn't remember which case was the issue.