Path: utzoo!utgpu!water!watmath!clyde!bellcore!faline!ulysses!allegra!mit-eddie!husc6!cmcl2!brl-adm!brl-smoke!gwyn
From: gwyn@brl-smoke.UUCP
Newsgroups: comp.lang.c
Subject: Re: exit(-1)
Keywords: exit, zero
Message-ID: <7045@brl-smoke.ARPA>
Date: 12 Jan 88 00:01:37 GMT
References: <502@cresswell.quintus.UUCP> <6935@brl-smoke.ARPA> <1179@wjvax.UUCP> <6983@brl-smoke.ARPA> <7208@ki4pv.uucp>
Reply-To: gwyn@brl.arpa (Doug Gwyn (VLD/VMB) <gwyn>)
Organization: Ballistic Research Lab (BRL), APG, MD.
Lines: 11
Posted: Mon Jan 11 19:01:37 1988

In article <7208@ki4pv.uucp> tanner@ki4pv.uucp (Dr. T. Andrews) writes:
-Great!  You've found a solution that the VMS folks could live with.
-Unfortunately, those few unlucky enough to not be using VMS have been
-spending their lives coding progs which finish with exit(0) when they
-worked.  How about a slap in the face with a wet towel to them?

Please pay more careful attention.  exit(0); is still a valid way of
reporting success under the proposed ANSI C.  I'm sure I said that.
However, exit(1); is not guaranteed to report failure on all systems.
The real need was for EXIT_FAILURE; EXIT_SUCCESS was introduced just
for symmetry and completeness.