From: "Mauricio Fernández" <batsman.geo@...>
Date: 2003-05-26T20:36:54+09:00
Subject: Re: Closures, capturing variables and evilness

On Mon, May 26, 2003 at 07:56:38PM +0900, ts wrote:
> >>>>> "M" == Mauricio =?iso-8859-1?Q?Fern=E1ndez?= <Mauricio> writes:
> 
> M>    def make_closure
> M>       p = proc { puts eval("bla") }
> M>       bla = "foo"
>  
>          local variable
> 
> M>    def make_closure
> M>       p = proc { puts bla }
> 
>          method
> 
> M>       bla = "foo"
> 
>          local variable

OK, this explains (2), but do we really want eval("someval") to work?
(ie. capture the whole environment regardless of "explicit" var. usage).

-- 
 _           _                             
| |__   __ _| |_ ___ _ __ ___   __ _ _ __  
| '_ \ / _` | __/ __| '_ ` _ \ / _` | '_ \ 
| |_) | (_| | |_\__ \ | | | | | (_| | | | |
|_.__/ \__,_|\__|___/_| |_| |_|\__,_|_| |_|
	Running Debian GNU/Linux Sid (unstable)
batsman dot geo at yahoo dot com

No, that's wrong too.  Now there's a race condition between the rm and
the mv.  Hmm, I need more coffee.
	-- Guy Maor on Debian Bug#25228