Hans-Martin Mosner wrote:
> 
> Sorry, that's my fault.
> It is a behavioral change in my BetterDebugger stuff. I have decoupled
> the 'restart' and 'proceed' functionality because I often want to reset the
> execution stack to the beginning of a method, without immediately proceeding.
> It's essentially the same behavior as in the VisualAge debugger.
> 
> Should there be a preference for this? I prefer the non-proceeding restart, but
> others might prefer to have it the old way.

I also greatly prefer the non-proceeding restart, so I guess a preference would be nice.

Probably a dumb question, but when is the usual proceeding restart useful?  I have to admit that I've never had (or perceived) a need to use it instead of just using 'proceed'.  I guess I can imagine some unusual situations, but it's much more often that I accidentally step over a method I wanted to send into, and I'd like a non-proceeding restart so I can try stepping through things again.

- Doug Way
  dway at riskmetrics.com