[squeak-dev] Re: Is this a bug with Step "Over"?

Chris Muller asqueaker at gmail.com
Sat Jun 20 15:44:55 UTC 2015

> Warning>>defaultAction
> "The user should be notified of the occurrence of an exceptional occurrence
> and given an option of continuing or aborting the computation. The
> description of the occurrence should include any text specified as the
> argument of the #signal: message."
> ToolSet
> debugContext: thisContext
> label: 'Warning'
> contents: self messageText, '\\Select Proceed to continue, or close this
> window to cancel the operation.' withCRs.
> self resume.
> contrast that with Halt's defaultAction:
> Halt>>defaultAction
> "No one has handled this error, but now give them a chance to decide how to
> debug it.  If none handle this either then open debugger (see
> UnhandedError-defaultAction)"
> UnhandledError signalForException: self
> With Halt's approach, the debugger can catch it, and catch subsequent halts;
> indeed the debugger can catch any unhandled exception raised within
> debugging.  But it can't, and shouldn't, squash the opeining of a debugger
> if the debugged code chooses to do so.
> One fix is to use Halt's defaultAction for Warning.  I think this is the
> right thing to do.  Another solution is to accept that Warning behaves
> bizarrely and leave it as is.  What do y'all think?

Hi Eliot, nobody's #defaultAction changed from 4.5 to 4.6 so why does
Warning work correctly in 4.5 but not 4.6?  I'm concerned the problem
may be deeper..

More information about the Squeak-dev mailing list