Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site amdahl.UUCP
Path: utzoo!dciem!nrcaero!pesnta!amdcad!amdahl!gam
From: gam@amdahl.UUCP (gam)
Newsgroups: net.lang.c
Subject: Re: SIZEOF
Message-ID: <1071@amdahl.UUCP>
Date: Thu, 31-Jan-85 19:42:00 EST
Article-I.D.: amdahl.1071
Posted: Thu Jan 31 19:42:00 1985
Date-Received: Fri, 1-Feb-85 21:40:30 EST
References: <347@ecr.UUCP> <393@rlgvax.UUCP> <260@gumby.UUCP>
Organization: Blue Mouse Trailer Resort, Hellmouth, CA
Lines: 22

> > Anyone who has made much effort at porting C code has encountered lots of
> > problems, all too many of which are due to people misusing the language.
> > Many of those can be avoided by using "lint".  Go forth and do so.
> > 
>    With regard to lint:
> 
>    1) Most people working in a Unix environment never use it, because they
>       don't have to.
>    Human nature being what it is, "go forth and use lint" should get approx-
> imately the same enthusiastic response as "go forth and sin no more."

Lint is widely used here.  On more than one occasion a casual misuse
of pointers or arrays were pointed out by lint.  Also lint gets almost
as much attention as the C compiler, as far as program maintanence
is concerned.  And porting programs from other systems would be
a painful task without lint.

People here aren't using lint because it is a good upright moral
thing to do; they use it because it helps to solve problems.  That's
what a good tool is for.
-- 
Gordon A. Moffett		...!{ihnp4,hplabs,sun}!amdahl!gam