From: Joel VanderWerf <vjoel@...>
Date: 2009-07-06T08:10:24+09:00
Subject: Re: to_proc and Proc/block conversion with &

David A. Black wrote:
> I think one issue is that there's no good term for the Proc that gets
> pressed into service as a block. It's not exactly a block, but just
> calling it a Proc doesn't serve to differentiate it from a Proc passed
> as a method argument.

"Eigenproc" ?  :P

> The common practice of using &block as the variable that "catches" the
> code block is kind of imprecise for the same reason: it's not a block
> that's bound to that variable, but a Proc. The term "block" tends to
> get spread out to mean more things than the block itself (the
> syntactic construct), which I think is kind of too bad but I'm not
> sure what the alternative is.

def foo(&proc_that_represents_the_callers_block)

... bah, I can't do better.

-- 
       vjoel : Joel VanderWerf : path berkeley edu : 510 665 3407