Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:46810
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.222.188 as permitted sender)
DomainKey-Status: bad
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :cc:content-type;
        b=sBiuMzFhrPro8BJa5xgobPUe85OFtFWTlS8056vw1z6LaMKwIcugRfsp/q77L6lbqu
         ZHSoLPaAkEgyn9jK1UL492gyPEars8HDEz1tXhXkNevwBQDwlK+nBF13fvk92MTM8X2R
         2wldqJRio9Dc1gkinWme1eFAjzo9wMUpgIK24=
MIME-Version: 1.0
In-Reply-To: <4B54FC87.8070106@zend.com>
References: <4B54FC87.8070106@zend.com>
Date: Tue, 19 Jan 2010 10:03:21 -0700
Message-ID: <e2e02fe1001190903n3037fd1br49a20eb5818a86d7@mail.gmail.com>
To: Stanislav Malyshev <stas@zend.com>
Cc: PHP Internals <internals@lists.php.net>
Content-Type: text/plain; charset=ISO-8859-1
Subject: Re: [PHP-DEV] function call chaining
From: chrisstocktonaz@gmail.com (Chris Stockton)

Hello,

On Mon, Jan 18, 2010 at 5:27 PM, Stanislav Malyshev <stas@zend.com> wrote:
> I wrote a small patch that enables this kind of syntax in PHP:
>
> foo()();
> ...

I think language enhancements with no BC breaks that offer a wider
toolset to programmers is a good thing. I would also like to see the
other ideas in this thread implemented such as array access & object
creation.

The only thing I do not like about this is I do not beleive it fits
the PHP error model. Lets just say Bar::foo($arg) returns a function
callback or FALSE/NULL on a error condition. So you end up with a
function call to something that is not callable, the PHP way under
this case is to have a fatal error. I would rather not see more ways
to cause fatal errors in PHP (call to undefined method has gotten a
bit more popular since object chaining has risen in popularity as
well). Of course I know exceptions are likely out of the question for
these kinds of cases as well. These thoughts do not apply to array
access or object creation.

Regards,

-Chris