Subject: Re: grf_cl.c tested on A2000+Spectrum1MB
To: Michael L. Hitch <email@example.com>
From: Christian E. Hopps <firstname.lastname@example.org>
Date: 02/05/1995 21:40:25
> > /* was a break -SG- */
> > return(0);
> Uh - doesn't a return(0) indicate an error? This routine looks like it
> returns 1 if everything is OK.
Of course with few exceptions functions should return their error status.
I trust that Michael is correct so I thought I would make the point that
people (i.e. driver authors) should be returning error states e.g.
return (-1); /* error */
return (0); /* no error */
This is the standard way to do things in NetBSD.