home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Usenet 1994 January
/
usenetsourcesnewsgroupsinfomagicjanuary1994.iso
/
sources
/
std_unix
/
v21
/
066
< prev
next >
Wrap
Internet Message Format
|
1990-12-05
|
1KB
From std-unix-request@uunet.uu.net Tue Aug 28 18:19:38 1990
Received: from cs.utexas.edu by uunet.uu.net (5.61/1.14) with SMTP
id AA04039; Tue, 28 Aug 90 18:19:38 -0400
Posted-Date: 28 Aug 90 03:44:10 GMT
Received: by cs.utexas.edu (5.64/1.74)
From: gwyn@smoke.brl.mil (Doug Gwyn)
Newsgroups: comp.std.unix
Subject: Re: Question about atexit()
Message-Id: <468@usenix.ORG>
References: <442@usenix.ORG> <450@usenix.ORG> <466@usenix.ORG>
Sender: std-unix@usenix.ORG
Organization: U.S. Army Ballistic Research Laboratory, APG, MD.
X-Submissions: std-unix@uunet.uu.net
Date: 28 Aug 90 03:44:10 GMT
Reply-To: std-unix@uunet.uu.net
To: std-unix@uunet.uu.net
From: Doug Gwyn <gwyn@smoke.brl.mil>
In article <466@usenix.ORG> karish@mindcrf.uucp (Chuck Karish) writes:
>>Doug Gwyn is right: specify the Standard C conformant option to POSIX
>>(or simply specify Standard C) and you'll get atexit().
>I disagree. Certainly if the customer specifies that a full
>implementation of standard C be part of the package, it will be
>present, but POSIX.1 doesn't require this.
And indeed I did NOT say what Donn's paraphrase suggests.
I said that if you need atexit() you should specify conformance
to the C standard (as well as any POSIX conformance that you need).
Volume-Number: Volume 21, Number 66