Article View: comp.std.unix
Article #147Re: Standards Update, IEEE 1003.4: Real-time Extensions
From: henry
Date: Fri, 08 Dec 1989 22:52
Date: Fri, 08 Dec 1989 22:52
19 lines
1268 bytes
1268 bytes
From: henry@utzoo.uucp
>From: Jeffrey S. Haemer <jsh@usenix.org>
>[threads vs signals] In fact,
>I think the early, simpler versions of signal() look a lot like what's
>needed (around V6 or so)...
Actually, it can be simpler yet, as Waterloo's Thoth system showed.
Subject to some sort of suitable protections (perhaps including a way
to ignore signals), when a thread receives a signal, it drops dead.
No signal handlers or blocking. If you want some sort of recovery
action, have another thread waiting for the first one to die: it has
access to all the first thread's data, so it can do whatever recovery
is appropriate.
Henry Spencer at U of Toronto Zoology
uunet!attcan!utzoo!henry henry@zoo.toronto.edu
Volume-Number: Volume 17, Number 96
Technical Details
Message-ID:
<469@longway.TIC.COM>Path:
arc1-ca.pugleaf.net!utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!uunet!longway!std-unixReferences:
<465@longway.TIC.COM>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!uunet!longway!std-unix From: henry@utzoo.uucp Newsgroups: comp.std.unix Subject: Re: Standards Update, IEEE 1003.4: Real-time Extensions Message-ID: <469@longway.TIC.COM> Date: 8 Dec 89 22:52:56 GMT References: <465@longway.TIC.COM> Sender: std-unix@longway.TIC.COM Reply-To: henry@utzoo.uucp Lines: 19 Approved: jsq@longway.tic.com (Moderator, John S. Quarterman)