spawn_monitor/3
Sean Hinde
earlyriser@REDACTED
Mon Sep 1 14:16:17 CEST 2003
Hi,
There was in interesting interchange between Mike Williams and Joe
Armstrong at the Erlang workshop on Friday about whether it was a
mistake to make link/1 bidirectional or not. The conclusion was that
both monitor and link were needed and that both are now provided with
the addition of the monitor/2 bif.
Maybe it is time to finish the job and add the atomic spawn_monitor/3
bif, which would prevent spawned processes killing the spawner (by
sending {'DOWN' etc instead of {'EXIT' etc)
The number of times I have made a process trap exits and then keep an
ets table of all known spawned worker processes just so that I can
respond correctly to 'EXIT' messages from elsewhere is getting quite
large, and a spawn_monitor bif would solve this very elegantly, apart
from the other advantages.
R10 maybe?
Sean
More information about the erlang-questions
mailing list