Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:66646
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.178 as permitted sender)
Message-ID: <51433530.5040707@gmail.com>
Date: Fri, 15 Mar 2013 15:50:24 +0100
User-Agent: Thunderbird
MIME-Version: 1.0
To: Steve Clay <steve@mrclay.org>
CC: PHP Internals <internals@lists.php.net>
References: <51432E01.7090502@mrclay.org>
In-Reply-To: <51432E01.7090502@mrclay.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Could we kill call_user_func?
From: keisial@gmail.com (=?ISO-8859-1?Q?=C1ngel_Gonz=E1lez?=)

On 15/03/13 15:19, Steve Clay wrote:
> I'm sure this question has been discussed before, so if anyone can
> point to me to links or briefly recap I'd appreciate it.
>
> Why can't we make $someCallable() always work? E.g. http://3v4l.org/FLpAq
>
> I understand the problem of $obj->foo() where ->foo is a callable
> property. The workaround could be:
>
> ($obj->foo)();
>
> call_user_func() just seems so ugly now that we have nicer syntax in
> so many other areas.
>
> Steve Clay
No.

What if I want to call functions with a variable number of arguments?

For instance, the common piece of a hook system implementation, where
the arguments of the functions called vary depending on the hook.