Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:93342
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain basereality.com from 209.85.213.43 cause and error)
MIME-Version: 1.0
Date: Sun, 15 May 2016 18:29:22 +0100
Message-ID: <CA+kxMuQxSj2enCXxZ50qgR-ehrvLEGJFjoc+xcyosN=6zowtjQ@mail.gmail.com>
To: "internals@lists.php.net" <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Subject: [RFC][VOTE] Closure from callable
From: danack@basereality.com (Dan Ackroyd)

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