Meyer, OO and concurrency

Vance Shipley <>
Thu Jul 14 23:41:05 CEST 2005

One can easily imagine an error handler which is simply never
called into duty.  Distinguishing that from a process which 
can't ever receive what it is waiting for would be impossible 
if you're allowed dynamic code loading.


On Thu, Jul 14, 2005 at 11:03:03PM +0200, Ulf Wiger wrote:
}  In Erlang, a process waiting indefinitely for something that
}  will never occur is probably (but not certainly) in a faulty
}  state. It is very difficult to determine that a message can
}  never be sent. Another process may be at fault, and the problem
}  may be fixed by changing and reloading a module in some other
}  part of the system.

More information about the erlang-questions mailing list