Session Summary: Exceptions and Concurrency Chair: Alexander Romanovsky R a p p o r t e u r : J6rg Kienzle Motivations The session chair started the session by pointing out that Ada has very elaborate features for handling concurrency, but that the exception handling model is basically sequentied. Some of the position papers and also his own experience provide evidence that concurrent systems often require concurrency-aware exception handling features, or even means to express collaborative exception handling. William Bail defined the situation very nicely: in sequential programming, any statement might depend on the previous statement. Sequential exception handling addresses this situation. In a concurrent setting, where exceptions might be raised in some other collaborating task, the dependency may be realized only later on, namely at the point where one of the tasks wants to talk to or use the results of the task that has got the exception. in one of the participant tasks should affect the execution of the other participating tasks. In such a situation, preemptive models will interrupt all other participating tasks and initiate cooperative error recovery. Such systems could benefit from a feature that allows a task to raise an exception in some
/lp/association-for-computing-machinery/exceptions-and-concurrency-xShtlpWtlz