With the first, you are not defining for the Error to be handled, only what to do when the stack unwinds abnormally.
In the second you are defining for the Error to be handled, so it does that. cheers -ben On Sat, 16 May 2020 at 01:00, Vitor Medina Cruz <vitormc...@gmail.com> wrote: > Hello, > > On Windows 10 and Pharo 8, If I do: > > [ Error signal ] ifCurtailed: [ Transcript show: 'error' ]. > > the debug window pops up, when I close, 'error' is print in the > Transcript. If I do > > [ Error signal ] on: Error do: [ Transcript show: 'error' ]. > > 'error' is print in Transcript without debug windows pops up. I was > expecting the same behavior here, as if ifCurtailed was a syntax sugar for > on:do:, that is not the case or it is some kind of error? The way it is, I > cannot use ifCurtailed because I don't want the debug window to pup up. > > Regards, > Vitor >
