Hi,

In message "Re: retry semantics changed"
    on Sat, 24 Nov 2007 07:19:32 +0900, Dave Thomas <dave / pragprog.com> writes:

|I'm thinking that allowing retry in a block still has the effect of  
|invoking the controlling method again, reevaluating its arguments.  
|This means that the issues of side effects are still present:

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.

							matz.