On Fri, 21 Sep 2001, Andrew Brown wrote:

> >> i expected it to have a non-zero exit status if it found something to
> >> complain about.
> >
> >that would be very un-unix like of it, and also contrary to one's usual
> >goals when running 'lint' from make, etc.  Usually you want to collect
> >the entire set of warnings and nits and then deal with them on a
> >priority basis.  in this case you're only interested if the lint process
> >fails because of some system or hardware error.
>
> un-unix like?  to give a non-zero exit status on error?  tell that to
> cc/gcc, grep, rm, dd, sendmail, make, cmp, diff, patch, fsck, etc.  :P

	"Error" implies "unable to complete its job". cc doesn't abort and
	exit when it generates warninig, why should lint?

-- 
		David/absolute		-- www.netbsd.org: No hype required --