Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:38467
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmx.net designates 213.165.64.20 as permitted sender)
To: internals@lists.php.net
Date: Fri, 20 Jun 2008 16:33:08 +0200
User-Agent: KMail/1.9.9
Cc: Larry Garfield <larry@garfieldtech.com>
References: <4856A547.3080801@gmx.net> <485B5BCC.1060003@city.ee> <200806200729.40623.larry@garfieldtech.com>
In-Reply-To: <200806200729.40623.larry@garfieldtech.com>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="utf-8"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-ID: <200806201633.08425.waqner@gmx.net>
Subject: Re: [PHP-DEV] [PATCH] [RFC] Closures and lambda functions in PHP
From: waqner@gmx.net (Alexander Wagner)

On Friday 20 June 2008, Larry Garfield wrote:
> > function ($x, $y) use ($a, $b, &$c) {};
>
> I am not sure if "use" is the clearest word to use there (wouldn't lexical
> there make more sense?)

I agree. "use" for both namespaces and closures may not be a good idea.
Otherwise +1 to this syntax for its low WTF-factor.
Look like parameters. Behave like parameters.

Also, allowing this for regular function definitions might be a nice long-term 
replacement for global.

> I would be fine with requiring an explicit declaration of $this if it helped
> avoid memory leaks. 

I would propose to always require explicit declaration of $this, even if there 
is no memory-leak problem. This would make it easier to distinguish plain 
lambdas from closures and would prevent closures from being created by 
accident.
As functional programming is foreign to most PHP-developers, better to err on 
the side of being explicit.

Gesundheit
  Wag

-- 
Her vocabulary was as bad as, like, whatever.