Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:76740
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.219.48 as permitted sender)
MIME-Version: 1.0
Sender: morrison.levi@gmail.com
In-Reply-To: <CAMVzVHOUMKZtDhohL=9gRcUz__D3bh9KFit3625B0k2dFAwmCQ@mail.gmail.com>
References: <C751B275-9F65-40F4-AAA7-F14645DA4CC0@ajf.me>
	<CAMVzVHOUMKZtDhohL=9gRcUz__D3bh9KFit3625B0k2dFAwmCQ@mail.gmail.com>
Date: Wed, 20 Aug 2014 13:30:10 -0600
Message-ID: <CAFMT4NoxiEnJfwDah5+K8tbfpjsEiohWEgKvR_CKSeV1b3ePRA@mail.gmail.com>
To: Nathan <nathan.bruer@starin.biz>
Cc: Andrea Faulds <ajf@ajf.me>, PHP Internals <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Subject: Re: [PHP-DEV] [VOTE][RFC] Closure::apply() (re-opening)
From: levim@php.net (Levi Morrison)

On Wed, Aug 20, 2014 at 11:51 AM, Nathan <nathan.bruer@starin.biz> wrote:
> The only thing I'd suggest is like I said in the last email is to make the
> syntax more like Closure::bind(Closure $closure, object $newThis, [mixed
> $newScope = 'static']) and make it Closure::apply(mixed $newObjectOrScope
> [, mixed ... $parameters]) $newObjectOrScope would then allow a user to
> supply a class name or an object. If class name is passed you have access
> to "static::", "self::", and "parent::" inside the function everything else
> works as described in the RFC.
>
> Give the ability to call a closure as a static method of a class or a
> normal method of an object. Right now the only way to do it is doing
> binding and creating new closures and calling those closures then
> destroying them.

I think you are confused. This proposal basically binds the closure to
the new object and invokes it immediately. I genuinely don't see how
it being statically bound to the object will make a difference. Please
elaborate.