From: Martin DeMello <martindemello@...>
Date: 2003-01-06T15:59:53+09:00
Subject: Re: Accessing a block's "receiver"

David Alan Black <dblack@candle.superlink.net> wrote:
> 
> Does "disaster" include causing all Ruby code to stop working? :-)
> 
> Even leaving that aside, it doesn't appeal to me.  In exchange for a
> few cases where you'd have to refactor (as above), you'd have
> thousands of cases where you'd see:
> 
>  obj.meth {|discard_me,a,b| ...}

No, I meant an implicit recv (much as method calls don't need an
explicit self). It'd break anything that used 'recv' as a variable name,
but everything else would continue to work transparently - they just
wouldn't use the passed in recv.

> You could use instance_eval:

<snip>

That's neat :) Never thought of instance_eval.

martin