Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.1 6/24/83; site umcp-cs.UUCP
Path: utzoo!linus!decvax!decwrl!amdcad!lll-crg!gymble!umcp-cs!chris
From: chris@umcp-cs.UUCP (Chris Torek)
Newsgroups: net.lang.c
Subject: exit() on VMS
Message-ID: <3174@umcp-cs.UUCP>
Date: Wed, 12-Feb-86 04:49:12 EST
Article-I.D.: umcp-cs.3174
Posted: Wed Feb 12 04:49:12 1986
Date-Received: Thu, 13-Feb-86 20:08:05 EST
References: <1046@decwrl.DEC.COM>
Organization: U of Maryland, Computer Science Dept., College Park, MD
Lines: 20

In article <1046@decwrl.DEC.COM> dyer@dec-vaxuum.UUCP (Jym Dyer) writes:
>> exit(0);
>
>   This isn't portable to VMS.  (-: Does anybody care about VMS,
>though? :-)  0 is an undefined status code in VMS!

I would hope that on VMS, exit(0) maps to status code 1 (success,
no error; it is possible on VMS to have failures without errors
and successes with errors), and that anything else maps to a status
that indicates an `unspecified error'.  VMS C should provide another
`exit'-like routine that actually just passes its argument on to
the termination system call.  Use of the *latter* routine would
be unportable, though preferred for VMS system programs.

(It might be feasible to have exit() map values from <sysexits.h>
to VMS status codes, I suppose.)
-- 
In-Real-Life: Chris Torek, Univ of MD Comp Sci Dept (+1 301 454 1415)
UUCP:	seismo!umcp-cs!chris
CSNet:	chris@umcp-cs		ARPA:	chris@mimsy.umd.edu