Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:93349
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain zend.com designates 157.56.111.115 as permitted sender)
To: Dan Ackroyd <danack@basereality.com>, "internals@lists.php.net"
	<internals@lists.php.net>
Thread-Topic: [PHP-DEV] [RFC][VOTE] Closure from callable
Thread-Index: AQHRrs94vEUA0EmG9kusUwZkqMJhqp+7O91X
Date: Mon, 16 May 2016 08:31:22 +0000
Message-ID: <CY1PR0201MB1786ACA85B5D9A04778C0E1CBF770@CY1PR0201MB1786.namprd02.prod.outlook.com>
References: <CA+kxMuQxSj2enCXxZ50qgR-ehrvLEGJFjoc+xcyosN=6zowtjQ@mail.gmail.com>
In-Reply-To: <CA+kxMuQxSj2enCXxZ50qgR-ehrvLEGJFjoc+xcyosN=6zowtjQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
spamdiagnosticoutput: 1:23
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-originalarrivaltime: 16 May 2016 08:31:22.9345
 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 32210298-c08b-4829-8097-6b12c025a892
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CY1PR0201MB1788
Subject: Re: [PHP-DEV] [RFC][VOTE] Closure from callable
From: dmitry@zend.com (Dmitry Stogov)

I'm sorry, I didn't follow the RFC discussion.
In general I like the idea, but why not to use Closure constructor?

$f =3D new Closure("some_func");

would look more readable than

$f =3D Closure::fromCallable("some_func");

Sorry, if this was already discussed before.

Thanks. Dmitry.

________________________________________
From: Dan Ackroyd <danack@basereality.com>
Sent: Sunday, May 15, 2016 8:29:22 PM
To: internals@lists.php.net
Subject: [PHP-DEV] [RFC][VOTE] Closure from callable

Hello,

I've opened the voting for the Closure from callable RFC -
https://wiki.php.net/rfc/closurefromcallable

Just to note, some people I've spoken to have expressed a desire to
have a more powerful syntax where 'bare' function names are used,
like:

callable(someFunctionName)
callable($this->method)

I fully agree with those people, however I can't see anyway to do that
before PHP 8. It would almost certainly need some clean up of the
allowed syntax to disambiguate what `$this->method` means for:

class Foo {
    public $method;
    public function method() { }
}

Leaving that top-level function name available for future versions,
where we might be able to support it properly, is one of the reasons
to use the more verbose function name.

cheers
Dan

--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php