Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:39150
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain pooteeweet.org from 88.198.8.16 cause and error)
Cc: internals@lists.php.net
Message-ID: <C9FD4EE6-9D1C-4E10-8860-A8559F05983E@pooteeweet.org>
To: Moriyoshi Koizumi <moriyoshi@at.wakwak.com>
In-Reply-To: <54FF091B-A4BE-4C3E-9783-D2DE93D6AF31@at.wakwak.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v928.1)
Date: Mon, 21 Jul 2008 23:01:00 +0200
References: <54FF091B-A4BE-4C3E-9783-D2DE93D6AF31@at.wakwak.com>
Subject: Re: [PHP-DEV] [PATCH] Allow use($var..) statement ubiquitously 
From: mls@pooteeweet.org (Lukas Kahwe Smith)


On 18.07.2008, at 01:23, Moriyoshi Koizumi wrote:

> Hi,
>
> Attached are the patches that allow the "use" statement that was  
> introduced with closures to appear within every function statement  
> except method definitions. I think this feature is a good addition  
> because it resolves inconsistency between closures and unticked  
> functions. In a nutshell,


I talked to Johannes, given that the thread has not garned much  
attention (maybe with this reply this will change) and the fact that  
since quite some time we have instead tried to encourage people to  
leverage $GLOBALS instead, it does not seem like we need to squeeze  
this new syntax into 5.3 so shortly before the feature freeze (I guess  
you get what you deserve by allowing closures in so late before the  
feature freeze?).

If we get feedback that end users that are new to PHP feel like they  
expect this syntax when they are exposed to closures we might want to  
add this in 5.4/6.0?

regards,
Lukas Kahwe Smith
mls@pooteeweet.org