Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!usc!apple!agate!alfa.berkeley.edu!bks
From: bks@alfa.berkeley.edu (Brad Sherman)
Newsgroups: comp.lang.c
Subject: Signal() and literate programming
Message-ID: <1990Jan19.193917.23671@agate.berkeley.edu>
Date: 19 Jan 90 19:39:17 GMT
Sender: usenet@agate.berkeley.edu (USENET Administrator;;;;ZU44)
Reply-To: bks@alfa.berkeley.edu (Brad Sherman)
Organization: University of California, Berkeley
Lines: 20


With respect to writing *portable* C:

Has anyone come up with what he/she thinks is a good way to
code signal handling.  Signal names and numbers are not
standardized.  We may wish to enable/ignore them at different
points in a program (without confusing the user of course). Not
all types of signals exist on all systems.

What I am after here is a way to localize (encapsulate?)
signal handling so that accommodating a new C environment
is simplified.  Probably a tougher issue is dealing
with questions of multiple signals arriving in quick
succession, but I welcome input on this as well.

Although I think that this is worthy of an open discussion,
if I receive e-mail I will summarize.
---
	Brad Sherman (bks@alfa.berkeley.edu)
Never attribute to stupidity that which can be explained by greed.