Date: Tue, 2 Feb 1999 11:22:01 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: Paul Derbyshire <pderbysh AT usa DOT net>
cc: djgpp AT delorie DOT com
Subject: Re: [semi OT] Signal support q
In-Reply-To: <3.0.6.32.19990201195416.008abbc0@pop.netaddress.com>
Message-ID: <Pine.SUN.3.91.990202112136.13819Q-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp AT delorie DOT com


On Mon, 1 Feb 1999, Paul Derbyshire wrote:

> How widespread is signal support beyond DJGPP? I'm given to understand that
> it is actually a feature of ANSI C, but in the real world this doesn't mean
> every C implementation offers it.

ANSI signal functionality is probably supported by everybody.  In
fact, DJGPP v1.x is the only case I know of that doesn't support
signals at all.

But you will get more meaningful info if you tell which signals do you
need to be supported, and what functionality do you need those signals
to produce.

For example, SIGSEGV is defined by ANSI, but old real-mode compilers
never actually generated that signal.  Which is okay by ANSI, btw,
since the standard says:

  "An implementation need not generate any of these signals, except as
  a result of explicit calls to the `raise' function."