Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!cs.utexas.edu!usc!ucsd!ucbvax!edison.cho.ge.com!rja From: rja@edison.cho.ge.com (rja) Newsgroups: comp.sys.ibm.pc.programmer Subject: Re: listing of errorlevel codes wanted Message-ID: <9006150233.AA20928@edison.CHO.GE.COM> Date: 15 Jun 90 02:33:08 GMT References: <1990Jun13.173331.15186@Octopus.COM> Sender: daemon@ucbvax.BERKELEY.EDU Reply-To: rja Organization: GE-Fanuc North America Lines: 21 In article <1990Jun13.173331.15186@Octopus.COM> someone wrote: [ stuff deleted here] >will do next..) Under OS/2 you can do multiple commands and conditional >commandline processing which throws this scheme off a little: >Commands which terminate with an ERRORLEVEL != 0 are considered SUCCESSFULL >and commands which terminate with an ERRORLEVEL 0 are failed (I believe >this is true under UNIX as well.. ) This is more or less conventional to >C and as we all know the DOS batch/command line evaluation is similar >to C. Hogwash. UNIX always uses exit(0) to indicate normal successful termination and always has used 0 to mean that and used non-zero to indicate some unusual termination. C has traditionally followed the UNIX convention (except on VMS, which has other problems). -- ______________________________________________________________________________ Internet (vastly preferable) : rja@edison.CHO.GE.COM UUCP (if you've got no choice): ...uunet!virginia!edison!rja ------------------------------------------------------------------------------ Friday (frai-de) n. The time when there are 2 days left in the workweek. ______________________________________________________________________________