Erlang's links http://erlang.org/doc/reference_manual/processes.html#id88612 http://erlang.org/doc/reference_manual/processes.html#id8861... are an interesting

Erlang's links http://erlang.org/doc/reference_manual/processes.html#id88612 http://erlang.org/doc/reference_manual/processes.html#id8861... are an interesting approach to this problem of failure signalling in a concurrent system. Stack-oriented exception handlers certainly don't work properly with concurrency. Two Erlang processes (~actors) can be linked together. If one then crashes (uncaught exception), the other one is automatically killed - unless it takes special steps to "trap exits", in which case it is sent a message describing the failure in its linked peer.