home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: gnu.gcc.bug
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!cis.ohio-state.edu!keinstr.UUCP!chaplin
- From: chaplin@keinstr.UUCP (Roger Chaplin)
- Subject: Re: How to use 'return' in c?
- Message-ID: <1992Nov6.231512.9705@keinstr.uucp>
- Followup-To: gnu.gcc.bug
- Sender: gnulists@ai.mit.edu
- Organization: Keithley Instruments, Cleveland, Ohio
- References: <1263@pascal.einstein.eds.com>
- Distribution: gnu
- Date: Fri, 6 Nov 1992 23:15:12 GMT
- Approved: bug-gcc@prep.ai.mit.edu
- Lines: 31
-
- Rich Wenner (wenner@einstein.eds.com) wrote:
- : In article <1992Nov4.231347.26999@u.washington.edu> chuckb@stein.u.washington.edu (Charles Bass) writes:
- : :After several people wrote me on the use of EXIT_SUCCESS and
- : :EXIT_FAILURE and their inability to locate those files on their
- : :systems I checked K&R 2ndEd for the definitive answer...
- :
- : Since when is K&R2 the Standard?
- :
- : :" void exit(int status)
- : :... How status is returned to the environment is
- : :implementation-dependent, but zero is taken as successful
- : :termination. The values EXIT_SUCCESS and EXIT_FAILURE may also
- : :be used." ^^^
- : :
- : :Because the word *may* is used I must assume that you either get
- : :it or you don't depending on your compiler/OS.
- :
- : Don't assume. RTFS, which simply states that these macros are defined in
- : stdlib.h. See section 4.10.
-
- <Sigh>. I just retrieved and built gcc-2.3.1, and these *still* aren't
- in there.
-
- Notice that followups are directed to gnu.gcc.bug.
-
- --
- Roger Chaplin / Instruments Division Engineering / 14 million women will not
- chaplin@keinstr.uucp / CI$: 76307,3506 / have the right to choose -
- #include <disclaimer.h> / they have been aborted.
- #include "disclaimer.h" /* cover all bases */ /
-
-