🚀 go-pugleaf

In <1992Apr3.182448.1894@cc.gatech.edu> arnold@cc.gatech.edu (Arnold Robbins) 
writes:

>|In article <4=kjtlc@dixie.com> eeh@dixie.com (Ed Howland) writes:
>|    I have been trying to find sources to a public domain version of lint,
>|    with little avail. Is the GNU project working on this?

>In article <NELSON.92Apr2210851@cheetah.clarkson.edu> nelson@sun.soe.clarkson.edu (Russ Nelson) writes:
>>Nope.  The idea is that gcc does what lint does, only it does it every time
>>you compile.  Damn good idea, too!

>Alas, this is not quite true.  GCC does most of what lint does.  At least one
>exception is cross-file checking.  GCC won't catch a function declared
>one way in one file and defined another way in another file.

Which is basically what lint was designed for, no?  There are many decent
ANSI compilers with good error-checking, but NONE of them can replace lint
because of this simple fact...

-- 
#include <disclaimer.h>			/* route all flames to /dev/null  */
/**************************************************************************/
/*   Systems Analyst      | John Steele     email: jsteele@netcom.com     */
/* Video Business Systems |                                               */
/*   1-800-255-3088       |    Most people spell COBOLSUX incorrectly...  */
/**************************************************************************/