home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Usenet 1994 January
/
usenetsourcesnewsgroupsinfomagicjanuary1994.iso
/
sources
/
std_unix
/
v21
/
045
< prev
next >
Wrap
Internet Message Format
|
1990-12-05
|
1KB
From news@cs.utexas.edu Mon Aug 20 18:22:07 1990
Received: from cs.utexas.edu by uunet.uu.net (5.61/1.14) with SMTP
id AA21167; Mon, 20 Aug 90 18:22:07 -0400
Posted-Date: 20 Aug 90 20:12:03 GMT
Received: by cs.utexas.edu (5.64/1.70)
id AA11788; Mon, 20 Aug 90 17:22:03 -0500
From: gwyn@smoke.brl.mil (Doug Gwyn)
Newsgroups: comp.std.unix
Subject: Re: Question about atexit()
Message-Id: <443@usenix.ORG>
References: <442@usenix.ORG>
Sender: std-unix@usenix.ORG
Organization: U.S. Army Ballistic Research Laboratory, APG, MD.
X-Submissions: std-unix@uunet.uu.net
Date: 20 Aug 90 20:12:03 GMT
Reply-To: std-unix@uunet.uu.net
To: std-unix@uunet.uu.net
From: Doug Gwyn <gwyn@smoke.brl.mil>
In article <442@usenix.ORG> sp@mysteron.osf.org (Simon Patience) writes:
>It was pointed out to me that atexit() is not defined in 1003.1
>1988.
IEEE Std 1003.1-1988 didn't explicitly specify atexit() for the ANSI C-
compatible variant because several people on P1003 didn't like it.
If in your procurement specifications you specify conformance to both
ANSI X3.159-1989 and IEEE Std 1003.1, then the ANSI C conformance
requirement suffices to guarantee the provision of atexit() facilities.
Volume-Number: Volume 21, Number 45