Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!rutgers!mit-eddie!genrad!decvax!tektronix!reed!nscpdc!joemu
From: joemu@nscpdc.NSC.COM (Joe Mueller)
Newsgroups: comp.lang.c
Subject: Re: ANSI C -- miscellaneous suggestions
Message-ID: <794@nscpdc.NSC.COM>
Date: Wed, 17-Dec-86 13:40:25 EST
Article-I.D.: nscpdc.794
Posted: Wed Dec 17 13:40:25 1986
Date-Received: Thu, 18-Dec-86 21:16:57 EST
References: <112@decvax.UUCP> <5458@brl-smoke.ARPA> <1171@ucbcad.BERKELEY.EDU>
Organization: National Semiconductor, Portland Development Center, Portland, OR
Lines: 18
Summary: exit status

In article <1171@ucbcad.BERKELEY.EDU>, faustus@ucbcad.BERKELEY.EDU (Wayne A. Christopher) writes:
> Regarding the requirement that exit(0) be success -- this will break a lot
> of VMS C programs, which use 1 for success and 0 for "undefined error"
> (I think -- I'm not a big VMS fan...)


The question of exit status came up again during the last meeting. The position
the committee eventually adopted is this:

exit(0) always indicates success (for unix code)
exit(EXIT_SUCCESS) always indicates success
exit(EXIT_FAILURE) always indicates failure
exit(anything else) implementation defined

The EXIT* macros will be defined in (I believe) stddefs.h.

							Joe Mueller
							...!nsc!nscpdc!joemu