> Why isn't it sufficient to test for UnhandledError instead? Otherwise, we would also need to test for Warning etc. ...

UnhandledError and UnhandledWarning are (private) implementation details of Squeak's exception handling mechanism. They should never be exposed to (or used by) applications/frameworks.

Best,
Marcel
Am 22.10.2019 18:50:59 schrieb Thiede, Christoph <christoph.thiede at student.hpi.uni-potsdam.de>:
Why isn't it sufficient to test for UnhandledError instead? Otherwise, we would also need to test for Warning etc. ...
Von: Squeak-dev <squeak-dev-bounces at lists.squeakfoundation.org> im Auftrag von Taeumel, Marcel
Gesendet: Dienstag, 15. Oktober 2019 13:18:26
An: gettimothy via Squeak-dev
Betreff: Re: [squeak-dev] The Trunk: System-mt.1093.mcz
 
Yeah, I wonder whether we should expand "Error" to "Error, Halt"?

Best,
Marcel
Am 15.10.2019 12:45:42 schrieb Balázs Kósi <rebmekop at gmail.com>:
Hi Hannes!

This morning I've just run into this exact same situation: putting a halt into a method, called by a morph's #drawOn:
makes the image unusable.


The problem stems from WorldState >> displayWorldSafely: being safe only for Errors and not for other kind of
Exceptions, and Halt being only an Exception not an Error.


For a quick fix add Halt to the handled exceptions in #displayWorldSafely:
[aWorld displayWorld. finished := true] on: Error, Halt do: [:ex |
Balázs
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.squeakfoundation.org/pipermail/squeak-dev/attachments/20191023/c67ae6a5/attachment-0001.html>