Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!henry
From: henry@utzoo.UUCP (Henry Spencer)
Newsgroups: net.lang.c
Subject: Re: SIZEOF
Message-ID: <5003@utzoo.UUCP>
Date: Sat, 2-Feb-85 20:01:27 EST
Article-I.D.: utzoo.5003
Posted: Sat Feb  2 20:01:27 1985
Date-Received: Sat, 2-Feb-85 20:01:27 EST
References: <347@ecr.UUCP> <393@rlgvax.UUCP>, <260@gumby.UUCP>
Organization: U of Toronto Zoology
Lines: 28

>    With regard to lint:
> 
>    1) Most people working in a Unix environment never use it, because they
>       don't have to.

Most people working in a Unix environment write cruddy code as a result.
Those of us with sense use lint at the drop of a bit, and delint other
people's code routinely [SIGH].

>    2) I have been desperately searching for an implementation for my own
>       programming environment (PC-DOS and QNX on the IBM PC), thus far
>       without any luck.  It just doesn't seem to be very available in any
>       but orthodox Unix systems.  This should say something about the great
>       esteem in which the C programming community holds lint.

Not quite true.  The relevant issue is not the value of lint, but the
total lack of any sort of public specifications for it.  The only way to
find out what lint does is to read the AT&T code, after which writing
one of your own is legally tricky.

>    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."

Generally, that's about the sort of response it gets from sloppy coders.
Those who take the advice to heart, generally come to appreciate its value.
-- 
				Henry Spencer @ U of Toronto Zoology
				{allegra,ihnp4,linus,decvax}!utzoo!henry