Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!linus!philabs!cmcl2!seismo!brl-smoke!smoke!lars@acc.arpa From: lars@acc.arpa Newsgroups: net.lang.c Subject: Re: Fast code and no morals Message-ID: <1015@brl-smoke.ARPA> Date: Mon, 17-Feb-86 17:57:00 EST Article-I.D.: brl-smok.1015 Posted: Mon Feb 17 17:57:00 1986 Date-Received: Wed, 19-Feb-86 20:29:15 EST Sender: news@brl-smoke.ARPA Lines: 31 > Date: 11 Feb 86 13:40:30 GMT > > > exit(0); > > This isn't portable to VMS. (-: Does anybody care about VMS, > though? :-) 0 is an undefined status code in VMS! > <_Jym_> dyer@dec-vaxuum.uucp > 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) I know this is naive, but then this flock is full of naive users... Doug, where exactly do Kernighan & Ritchie specify the semantics of the exit() procedure ? The common semantics seem to me to be "return to the surrounding operating system level, using the argument value as the return code". Unfortunately for portability, UN*X and VMS have different ideas about the semantics of program return codes, but you can't say VMS is WRONG just because it's DIFFERENT unless you can quote chapter and verse. Does the ANSI draft specify semantics for system calls ? / Lars Poulsen Advanced Computer Communications ------