Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:119702
Message-ID: <d1666f4b-7417-4cae-9aa0-2296a1462afb@gmail.com>
Date: Tue, 14 Mar 2023 23:09:05 +0000
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101
 Thunderbird/102.8.0
Content-Language: en-GB
To: internals@lists.php.net
References: <8a9a04b3-45e6-47dd-dee8-0f524e49bd37@gmail.com>
 <f0b6ce61-9a9f-4598-aa97-df6ceef6be28@app.fastmail.com>
In-Reply-To: <f0b6ce61-9a9f-4598-aa97-df6ceef6be28@app.fastmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Brainstorming idea: inline syntax for lexical
 (captured) variables
From: rowan.collins@gmail.com (Rowan Tommins)

On 14/03/2023 22:54, Larry Garfield wrote:
> However, I agree with Ilija that the original proposal to just do it automatically would be better; and if that didn't pass, I have no expectation that an alternate with a funky new syntax would do any better.


Well, a large part of my resistance to automatic capture is that it 
makes variable scope less visible at a glance. This avoids that by still 
having a marker for "I am from another scope", but a much less verbose 
one than the current use() clause.

I may be in a minority of one on that point, though, for all I know.


> The other concern is that this introduces a whole new realm of possible behaviors...

That's kind of where the closure thought came from - it seemed a very 
close analogue, so having one syntax for both feels natural. Outside of 
those cases, though, there's no reason it should mean anything, just as 
$this->foo or self::$foo doesn't mean anything outside a class. In fact, 
it could be spelled capture::$foo or $scope->foo rather than just using 
new punctuation, if we wanted to encourage that analogy.


Regards,

-- 
Rowan Tommins
[IMSoP]