Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:87961
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.220.49 as permitted sender)
To: Bob Weinand <bobwei9@hotmail.com>, PHP Internals <internals@lists.php.net>
References: <BLU436-SMTP13020F8CE8795C628BDC665E26B0@phx.gbl>
Message-ID: <55E4C19F.4060704@gmail.com>
Date: Mon, 31 Aug 2015 14:05:35 -0700
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:38.0)
 Gecko/20100101 Thunderbird/38.2.0
MIME-Version: 1.0
In-Reply-To: <BLU436-SMTP13020F8CE8795C628BDC665E26B0@phx.gbl>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] [RFC] [Discussion] Short Closures
From: smalyshev@gmail.com (Stanislav Malyshev)

Hi!

> I had this RFC in draft since some time, but delayed it due to all
> the ongoing PHP 7 discussions. Also we have no master branch to merge
> features in until 5.4 EOL. Thus I'm reviving this now.
> 
> Time for the first RFC targeting PHP 7.1 (assuming PHP 8 isn't going
> to be the next version ;-)):
> 
> The short Closures RFC: https://wiki.php.net/rfc/short_closures

I personally don't see much advantage in making PHP code less readable
and harder to parse. Also, "automatically use () all of the (compiled)
variables" does not look like a good idea - first, users have no idea
what compiled variables are, so the result would be unpredictable for
them, second, if there are a lot of variables in the scope (like global
scope) it would have huge performance costs for no gain.
Also, this syntax does not allow "use by-ref" which the existing syntax
does allow.

I think we already have syntax for anonymous functions and it works. The
only addition in this RFC is automatically gobbling up all local
variables, which in vast majority of use cases is not what the function
needs.
-- 
Stas Malyshev
smalyshev@gmail.com