> Synchronous exceptions present enough difficulties without
> asychronous ones. A possible systemic difference is that
> while it is common to make synchronous exceptions equivalent
> to non-local gotos, that is, there's no retry, asynchronous exceptions
> should probably permit continuation.

Actually, that's how signal handlers work in Caml (like in C): a
user-specified function is called at the earliest possible moment.
However, that function may choose to raise an exception (that's what I
called and asynchronous exception), and that's where the problems
Joerg mentioned occur.

- Xavier Leroy