Path: utzoo!utgpu!water!watmath!clyde!rutgers!gatech!bloom-beacon!husc6!cmcl2!brl-adm!brl-smoke!gwyn
From: gwyn@brl-smoke.ARPA (Doug Gwyn )
Newsgroups: comp.lang.c
Subject: Re: OS-dependent functions
Keywords: ANSI C operating systems signal()
Message-ID: <7074@brl-smoke.ARPA>
Date: 13 Jan 88 19:45:16 GMT
References: <590@mcrware.UUCP>
Reply-To: gwyn@brl.arpa (Doug Gwyn (VLD/VMB) <gwyn>)
Organization: Ballistic Research Lab (BRL), APG, MD.
Lines: 10

In article <590@mcrware.UUCP> jejones@mcrware.UUCP (James Jones) writes:
>If operating system-dependent functions don't fall under the umbrella of the
>ANSI C standard, and I agree that they shouldn't, then what is signal() doing
>in the ANSI Draft standard?

You could also ask what getchar() is doing in the draft standard.

Practically all operating systems can provide the minimal ANSI C
signal() functionality, and it was considered to be something of
real use to applications.