Exceptions in the context of concurrent Eiffel programming (i.e. SCOOP) are implemented using a straightforward policy: the program is halted as soon as the exception occurs. Here I show why sometimes a programmer cannot really avoid this default behavior even with a rescue clause. A more flexible mechanism is therefore desirable. I introduce an exception model viable in the context of concurrent processors, and respectful of the exception model already in use in single-threaded programs.

It's been quite some time since my last blog entry. I must confess: I abandoned Eiffel as my language of choice for a little while, to do some C++ and C#. It turns out that after I left my employer, I started working on a project of mine, with the firm intention to achieve it, make it professional but also to finish it fast.

I was truly thrilled when I first came across exceptions in C++ after using the clumsy error reporting style of C. It made my algorithms cleaner and, therefore, it made me happy. After several years, I tried Java and I found it interesting to impose the discipline of explicitly declaring the exceptions that may be raised in a routine.