Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!usc!zaphod.mps.ohio-state.edu!uakari.primate.wisc.edu!aplcen!uunet!usenix!std-unix
From: gwyn@smoke.brl.mil (Doug Gwyn)
Newsgroups: comp.std.unix
Subject: Re: Question about atexit()
Message-ID: <443@usenix.ORG>
Date: 20 Aug 90 20:12:03 GMT
References: <442@usenix.ORG>
Sender: std-unix@usenix.ORG
Organization: U.S. Army Ballistic Research Laboratory, APG, MD.
Lines: 14
Approved: jsq@usenix.org (Moderator, John Quarterman)
X-Submissions: 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