Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:76327
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain thomasbley.de from 85.13.137.24 cause and error)
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
User-Agent: ALL-INKL Webmail 2.11
In-Reply-To: <D17EB1B8-7A7E-419B-AF55-0ADCAB4CFEB3@ajf.me>
References: <D17EB1B8-7A7E-419B-AF55-0ADCAB4CFEB3@ajf.me>
To: internals@lists.php.net
Cc: ajf@ajf.me
Message-ID: <20140804005307.0B5CC261BFB@dd15934.kasserver.com>
Date: Mon,  4 Aug 2014 02:53:07 +0200 (CEST)
Subject: Re: [PHP-DEV] [RFC] Closure::call and Function Referencing as Closures
From: mails@thomasbley.de ("Thomas Bley")

Hello Andrea,

from userland perspective, I would prefer to open the Closure constructor instead of adding new syntax:

$qux = new FooBar(3);
// $func = &FooBar::getStatic;
$func = new Closure(array('FooBar', 'getStatic'));
$func($qux); // 3

Regards
Thomas


Andrea Faulds wrote on 03.08.2014 23:50:

> Good evening,
> 
> I am proposing two new RFCs. As they are both inter-related and complementary,
> with the second having the first as a prerequisite, I’m making just a single
> email to cover both:
> 
> https://wiki.php.net/rfc/closure_apply
> https://wiki.php.net/rfc/function_referencing
> 
> Both have written, tested and working patches aimed for master.
> 
> Thoughts appreciated, thanks.
> --
> Andrea Faulds
> http://ajf.me/
> 
> 
> 
> 
> 
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>