Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!gatech!uflorida!haven!adm!smoke!gwyn
From: gwyn@smoke.BRL.MIL (Doug Gwyn)
Newsgroups: comp.std.c
Subject: Re: how to exit from a signal routine
Keywords: ANSI, longjmp, signal
Message-ID: <10504@smoke.BRL.MIL>
Date: 7 Jul 89 13:33:42 GMT
References: <7997@cbnews.ATT.COM>
Reply-To: gwyn@brl.arpa (Doug Gwyn)
Organization: Ballistic Research Lab (BRL), APG, MD.
Lines: 16

In article <7997@cbnews.ATT.COM> mark@cbnews.ATT.COM (Mark Horton) writes:
>Is this something that should be fixed in the ANSI C standard?

No -- The Standard doesn't create the problem, it merely documents it.

There is no prohibition against C implementations doing a better job
than the minimum guaranteed by the C Standard.  In fact the C Standard
guarantees very little about signal behavior, because of the wide
variety of signal() implementations in existence.  Remember that the
C Standard is not UNIX specific, but rather applies to all operating
systems.

IEEE Std 1003.1 (POSIX) provides specifications for a much more
reliable signal mechanism.  Presumably UNIX-like implementations will
provide the extended POSIX signal support rather than merely a minimal
ANSI C facility for signals.