Also, #ifCurtailed: is supposed to fire if there's a long return that would
have passed through it, while #on:do: doesn't care about long returns in
the least.
On Sat, 16 May 2020 at 15:27, Ben Coman wrote:
> With the first, you are not defining for the Error to be handled,
> only what to do whe
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
wrote:
> Hello,
>
> On Windows 10 and Ph
Thanks!
I will use on:do: so.
On Fri, May 15, 2020 at 2:12 PM Richard Sargent <
richard.sarg...@gemtalksystems.com> wrote:
> On Fri, May 15, 2020 at 10:00 AM Vitor Medina Cruz
> wrote:
>
>> Hello,
>>
>> On Windows 10 and Pharo 8, If I do:
>>
>> [ Error signal ] ifCurtailed: [ Transcript show: '
On Fri, May 15, 2020 at 10:00 AM Vitor Medina Cruz
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
>
That is correct. It isn't curtail
