Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:39652
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain zend.com designates 212.25.124.163 as permitted sender)
Message-ID: <4897F54F.7080909@zend.com>
Date: Tue, 05 Aug 2008 10:38:07 +0400
User-Agent: Thunderbird 2.0.0.16 (Windows/20080708)
MIME-Version: 1.0
To: Moriyoshi Koizumi <moriyoshi@at.wakwak.com>
CC: Marcus Boerger <helly@php.net>, internals@lists.php.net
References: <909776579.20080803142659@marcus-boerger.de> <4896A7C4.8090503@zend.com> <4110083360.20080804104233@marcus-boerger.de> <4896EA3C.6010203@zend.com> <4897E9B5.9020006@at.wakwak.com>
In-Reply-To: <4897E9B5.9020006@at.wakwak.com>
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Inconsistencies in 5.3
From: dmitry@zend.com (Dmitry Stogov)

Allowing "use" inside function body assuming allowing it everywhere.

$x = function($arg) {
		if ($arg) {
			use $a;
		} else {
			use $b;
		}
	};

I don't like such ability and of course we won't be able to use "use" 
keyword as it will conflict with import statement.

Thanks. Dmitry.


Moriyoshi Koizumi wrote:
> Dmitry Stogov wrote:
>>
>>
>> Marcus Boerger wrote:
>>> Hello Dmitry,
>>>
>>> Monday, August 4, 2008, 8:55:00 AM, you wrote:
>>>
>>>> Hi Marcus,
>>>
>>>> see below
>>>
>>>> Marcus Boerger wrote:
>>>>> Hello Internals,
>>>>>
>>>>>   please let's not introduce new inconsistencies. Rather lets make new
>>>>> stuff consistent with old stuff during the alpha phase of 5.3.
>>>>>
>>>>> 1) new keyword 'use'. Semantically it is the same as 'static' or 
>>>>> 'global'
>>>>> so it should be used in the same location.
>>>
>>>> For me 'use' is the best keyword as it says that closure uses 
>>>> variables from current content. (the same keyword is used for import 
>>>> from namespaces)
>>>
>>> To be clear, I wasn't complaining about the keyword per se. I just 
>>> prefer
>>> it to be inside the curly braces of a closure next to global rather 
>>> than in
>>> front of it.
>>>
>>
>> No. The list of lexical variables is a part of the closure definition.
>>
>> The earlier implementation had "lexical" keyword which worked as you 
>> are suggesting, but it was much unclear.
> 
> I don't think there are many differences in ambiguity between
> 
> $closure = function ($arg) { use $a;
>   ...
> };
> 
> and
> 
> $closure = function ($arg) use ($a) {
> };
> 
> Moriyoshi
>