Daniel Schierbeck wrote:
>> :) In truth, I think I'm in favour of this change, especially if it
>> could be done so that the rescue catches exceptions from the block _as
>> well_ as those from the method to which the block is attached (if any).
> 
> I'm not sure I'd like that -- I see a block attached to a method call as
> being, in some sense, a child of that call, another kind of argument if
> you will; having the child rescue exceptions raised by the parent seems
> unintuitive to me, though others may feel different.

I agree with Daniel.  It should only rescue exceptions raised in the 
block, not the parent/holder/caller/receiver of the block.

Pistos

-- 
Posted via http://www.ruby-forum.com/.