Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:66644
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.175 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <51432E01.7090502@mrclay.org>
References: <51432E01.7090502@mrclay.org>
Date: Fri, 15 Mar 2013 15:21:26 +0100
Message-ID: <CALtuQzAMr4zJD-7krTL1P5VWxTObwqpKWyboUF92fi2hsoPeSg@mail.gmail.com>
To: Steve Clay <steve@mrclay.org>
Cc: PHP Internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=e89a8f3ba6e3f5484504d7f75bb0
Subject: Re: [PHP-DEV] Could we kill call_user_func?
From: krebs.seb@gmail.com (Sebastian Krebs)

--e89a8f3ba6e3f5484504d7f75bb0
Content-Type: text/plain; charset=ISO-8859-1

2013/3/15 Steve Clay <steve@mrclay.org>

> 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.
>

You don't need to use it, if you don't like it.


>
>
> Steve Clay
> --
> http://www.mrclay.org/
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>


-- 
github.com/KingCrunch

--e89a8f3ba6e3f5484504d7f75bb0--