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. On Wed, Aug 20, 2014 at 7:50 AM, Andrea Faulds <a...@ajf.me> wrote: > Good afternoon, > > I’m putting this RFC to a vote again as I haven’t heard any objections in > the past three days, and in the event something’s been missed, one week > would be long enough to spot it. > > Vote is here: https://wiki.php.net/rfc/closure_apply#vote > > It ends 2014-08-27. Thanks! > -- > Andrea Faulds > http://ajf.me/ > > > > > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php > >
