Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!uakari.primate.wisc.edu!dogie.macc.wisc.edu!decwrl!fernwood!oracle!news
From: fmcwilli@oracle.oracle.com (Floyd McWilliams)
Newsgroups: comp.lang.c
Subject: Re: An overview ...
Summary: Don't toss out lint
Message-ID: <1990Jul12.151618.16133@oracle.com>
Date: 12 Jul 90 15:16:18 GMT
References: <1990Jul1.065531.18620@acc.stolaf.edu>
Reply-To: fmcwilli@oracle.com (Floyd McWilliams)
Organization: Oracle Corporation, Belmont, CA
Lines: 17

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.

	I work for Oracle's kernal development group.  Everyone here knows
C; many of us are gurus.  But nobody is going to wade through thousands of
lines of code every time we change a structure, alter calling conventions,
or add new code.
	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."