On Nov 23, 2007, at 4:53 PM, Yukihiro Matsumoto wrote:

> I understand, but does side effect issue matter?  The primary reason
> of retry removal is performance.  By allowing method re-invocation,
> every method call requires context saving for possible retry in the
> method.  For retry in the blocks, context is saved anyway to implement
> break/next/redo etc.  Note that I am not opposing for dedicating retry
> for exception handling.  But we have make things clear before making
> incompatible change.


OK, I didn't understand the performance issues driving the decision.

The benefit of this change is that retry is now closer in user to  
redo, next, etc...



Cheers


Dave