Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!uakari.primate.wisc.edu!aplcen!boingo.med.jhu.edu!haven!adm!smoke!gwyn
From: gwyn@smoke.brl.mil (Doug Gwyn)
Newsgroups: comp.lang.c
Subject: Re: Funny mistake
Message-ID: <15547@smoke.brl.mil>
Date: 22 Mar 91 20:52:08 GMT
References: <1891@array.UUCP> <1991Mar21.021504.25553@murdoch.acc.Virginia.EDU> <1778@bbxsda.UUCP>
Organization: U.S. Army Ballistic Research Laboratory, APG, MD.
Lines: 10

In article <1778@bbxsda.UUCP> scott@bbxsda.UUCP (Scott Amspoker) writes:
>Well I'm not one of them.  I agree completely.  I see no reason to
>run a source file through lint prior to the C compiler everytime I
>make a change when I could enable certain desireable warning messages
>(of mistakes I frequently make) within the compiler.

Compiler options for lint-like warnings are fine with me,
so long as they are normally suppressed.  However, "lint"
does things that compilers normally do not, such as
checking external linkages against definition files.