Path: utzoo!attcan!uunet!cs.utexas.edu!tut.cis.ohio-state.edu!pt.cs.cmu.edu!andrew.cmu.edu!ghoti+
From: ghoti+@andrew.cmu.edu (Adam Stoller)
Newsgroups: comp.lang.c
Subject: Re: Can lint help an ANSI-C programmer?
Message-ID: <caNG2OS00as90XZ11a@andrew.cmu.edu>
Date: 31 May 90 13:48:10 GMT
References: <6328.265D8157@puddle.fidonet.org> <1754@tkou02.enet.dec.com> <00937758.16FBE220@rigel.efd.lth.se>,<24660@mimsy.umd.edu>,
	<009377E6.C32DAB80@rigel.efd.lth.se>
Organization: Information Technology Center, Carnegie Mellon, Pittsburgh, PA
Lines: 16
In-Reply-To: <009377E6.C32DAB80@rigel.efd.lth.se>

Excerpts from netnews.comp.lang.c: 31-May-90 Re: Can lint help an
ANSI-C.. e89hse@rigel.efd.lth.se (1405)

>  Well, I've found that 99% of the times I write: printf("name=%s\n"); I
> just don't care about the return value... Lint warnings about igonred
> return values have never helped me up to now, just bothered me. (BTW if
exit() is properly declared there won't be any warning.)


You may not care about the return value - but does your compiler take
the time to warn you that you didn't supply a needed argument to the
printf() call??

(does lint warn about this?)

--fish