Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!lll-crg!mordor!sri-spam!ames!ucbcad!ucbvax!decvax!mcnc!ravi
From: ravi@mcnc.UUCP (Ravi Subrahmanyan)
Newsgroups: comp.sys.atari.st
Subject: Signals in MWC (was outdated ranlib from Mark Williams)
Message-ID: <1868@alvin.mcnc.UUCP>
Date: Thu, 11-Dec-86 21:19:31 EST
Article-I.D.: alvin.1868
Posted: Thu Dec 11 21:19:31 1986
Date-Received: Sun, 14-Dec-86 14:58:27 EST
References: <22117737@decvax.UUCP> <119100001@exunido.UUCP>
Reply-To: ravi@alvin.UUCP (Ravi Subrahmanyan)
Distribution: world
Organization: Microelectronics Center of NC; RTP, NC
Lines: 20
Keywords: signals Mark williams C
Summary: It's a dummy, isn't it?

In article <119100001@exunido.UUCP> at@exunido.UUCP writes:
>Btw. has anyone experience with signals on MWC ? I tried to catch SIGHUP
>and got a nice crash .
>
>	Andreas Toenne

	In my version of MW C, the signal stuff is just a do-nothing
function, it seems to be there solely for letting existing code with
signal calls to compile without complaints (there's a small comment
and a one-line function declaration at the end of signal.h).  

	Actually, what's the deal with signal handling in general on
the ST when using C?  It doesn't seem as if TOS etc. allow functions of
the nature of SIGNAL() to be implemented easily, or at least not with
the functionality in, say, BSD:  the discussions re. trapping ^C's, or
Moshe Braner's attempts to set up the resident assassin seem to indicate
that.  This is something I'd very much like to see some discussion on,
I'm sure many others would too.  Anyone knowledgeable care to start it
off?
							-ravi