Path: utzoo!mnetor!uunet!husc6!yale!cmcl2!brl-adm!brl-smoke!gwyn
From: gwyn@brl-smoke.ARPA (Doug Gwyn )
Newsgroups: comp.lang.c
Subject: Re: exit(-1)
Message-ID: <7133@brl-smoke.ARPA>
Date: 19 Jan 88 15:09:37 GMT
References: <502@cresswell.quintus.UUCP> <6935@brl-smoke.ARPA> <1179@wjvax.UUCP> <1185@wjvax.UUCP> <1225@nmtsun.nmt.edu>
Reply-To: gwyn@brl.arpa (Doug Gwyn (VLD/VMB) <gwyn>)
Organization: Ballistic Research Lab (BRL), APG, MD.
Lines: 20

In article <1225@nmtsun.nmt.edu> hydrovax@nmtsun.nmt.edu (M. Warner Losh) writes:
>Why would you expect an operating system dependent scheme such as exit(0)
>to work on all OS's?  The whole world isn't using UNIX.

You guys have gotten confused.

X3J11, including the VMS C implementor, agreed to the following:

	#include <stdlib.h>	/* defines EXIT_SUCCESS & EXIT_FAILURE */

	exit(0);		/* indicates success on all OSes */
	exit(EXIT_SUCCESS);	/* indicates success on all OSes */
	exit(EXIT_FAILURE);	/* indicates failure on all OSes */

If, as you report, VMS C does not currently map exit(0) to something
sensible, that will have to be fixed before VMS C is ANSI-conforming.

>%NONAME-W-NOMESSAGE, No message text for message 0000000

Certainly this is not something that is essential to preserve on VMS!