🚀 go-pugleaf

On 11 Jun 90 23:44:51 GMT,
silver@xrtll.uucp (Hi Ho Silver) said:
> In article <Jun.11.13.23.51.1990.1616@zeppelin.rutgers.edu> sarra@zeppelin.rutgers.edu (William) writes:
> $Does anyone out there have a listing of the errorlevel codes and their
> $respective meanings?  If so, would you please send it to me, I have a
> $need for it's use in an assembly language program.

>    There are no assigned meanings to errorlevel codes.  It's up to the
> designer of each program to determine what results should be returned
> using the return value you read with errorlevel, and to assign numbers to
> these.

Sure there are standards (loose ones anyway!), and they come from
where all the good DOS programming ideas come from (Unix).

	Return Code	Meaning
	0		No Errors
	1		Something went wrong (often in parameters or data)
	2-infinity	Something else went wrong

These codes are used as valuse to exit() or return in C programs for
example.

For commands that test expressions like 1 == x usually return 0 if
assertion is false, 1 if assertion in true, and 2 if there is a syntax
error or something else. Documentation for the program should define
what the exit codes are. Better error messages also relieve one from
worrying about what these codes mean.


--

Frank Kolakowski 

======================================================================
|lfk@hx.lcs.mit.edu                     ||      Lee F. Kolakowski    |
|kolakowski@tropicana.mit.edu           ||	M.I.T.		     |
|lfk@mbio.med.upenn.edu		        ||	Dept of Chemistry    |
|AT&T:  1-617-253-1866                  ||	Room 18-506	     |
|#include <litigate.h>         		||	77 Massachusetts Ave.|
|                                    	||	Cambridge, MA 02139  |
|--------------------------------------------------------------------|
|		           One-Liner Here!                           |
======================================================================