Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:109033
To: internals@lists.php.net
References: <DM5PR07MB3067D2DEAD4B3C85FBDFD559F9F80@DM5PR07MB3067.namprd07.prod.outlook.com>
Message-ID: <77731b0f-70d9-788c-f6bf-7663542aaa7b@gmail.com>
Date: Sun, 15 Mar 2020 17:50:08 +0000
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101
 Thunderbird/68.6.0
MIME-Version: 1.0
In-Reply-To: <DM5PR07MB3067D2DEAD4B3C85FBDFD559F9F80@DM5PR07MB3067.namprd07.prod.outlook.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-GB
Subject: Re: [PHP-DEV] RFC idea: Block scoped variables with "let $x = expr"
From: rowan.collins@gmail.com (Rowan Tommins)

Hi Tyson,

I think this is an interesting idea, but the way you describe it does 
seem to introduce a lot of caveats and additional restrictions.

For instance, this feels very odd to me:

> Correctness would be enforced as a best-effort at compile-time - the variables would continue to only be freed at the end of the function call.


Intuitively, I would expect this:

{
     let $x = new Foo;
     $x->bar();
}
somethingElse();

to be equivalent to this:

let $x = new Foo;
$x->bar();
unset($x);
somethingElse();


Could you explain a bit more what the difficulties are in implementing 
it this way?

Regards,

-- 
Rowan Tommins (né Collins)
[IMSoP]