Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!watmath!clyde!burl!ulysses!allegra!mit-eddie!think!harvard!seismo!brl-smoke!smoke!jon@csvax.caltech.edu From: jon@csvax.caltech.edu Newsgroups: net.lang.c Subject: Re: Fast code and no morals Message-ID: <1092@brl-smoke.ARPA> Date: Tue, 18-Feb-86 23:02:21 EST Article-I.D.: brl-smok.1092 Posted: Tue Feb 18 23:02:21 1986 Date-Received: Fri, 21-Feb-86 07:07:19 EST Sender: news@brl-smoke.ARPA Lines: 31 > > Date: Sat, 15 Feb 86 21:43:34 EST > > > > If VMS does not support exit(0) as successful termination, > > then VMS is WRONG and needs to fix their exit() routine. > > Doug Gwyn (VLD/VMB) > > ... > Does the ANSI draft specify semantics for system calls ? > > / Lars Poulsen > Advanced Computer Communications > To be nitpicking, exit() is not a system call, although it probably invokes one. In answer to the question, the April 30 1985 draft says (Section D.10.4.2): void exit(int status); Finally, control is returned to the host environment. If the value of status is zero, the status returned is SUCCESSFUL TERMINATION; otherwise an implementation-defined form of the status UNSUCCESSFUL TERMINATION is returned. Currently exiting with status 0 on VMS generates a message complaining about the unknown exit status 0. I find this most annoying in trying to port code from Unix (actually there are lots of other misfeatures of VMS that qualify as MOST annoying, but...) -- Jon Leech (jon@csvax.caltech.edu) __@/