Path: utzoo!utgpu!watserv1!watmath!att!rutgers!cs.utexas.edu!uunet!unhd!al
From: al@uunet!unhd (Anthony Lapadula)
Newsgroups: comp.lang.c
Subject: Re: An overview ...
Message-ID: <1990Jul15.194736.11447@uunet!unhd>
Date: 15 Jul 90 19:47:36 GMT
References: <1990Jul1.065531.18620@acc.stolaf.edu> <1990Jul12.151618.16133@oracle.com>
Reply-To: al@unhd.UUCP (Anthony Lapadula)
Organization: Computing Information Services, University of New Hampshire
Lines: 20

In article <1990Jul12.151618.16133@oracle.com> fmcwilli@oracle.com (Floyd McWilliams) writes:
>In article <1990Jul1.065531.18620@acc.stolaf.edu> hannum@haydn.psu.edu (Charles Hannum) writes:
>>My solution:  Don't use lint; it's ancient and brain-dead.  Learn C, or get
>>a C guru to help you.
>
>	Lint is an automated tool that checks for simple errors.  It catches
>most of these errors and returns some spurious messages, which means the
>person running line must spend a few minutes checking them out.  Beats
>poring over the code for several hours with a copy of K&R II.
>
>--
>	Floyd McWilliams -- fmcwilli@oracle.com
>	"Little bunny Foo-foo, rocking out for Satan.
>	 Picking up little field mice and biting off their heads."

True, but I've yet to see a version of lint that understands prototypes.
Anyone know where I might find source code for such a beast?

-- Anthony Lapadula
No cute .sigs allowed!