Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!allegra!mit-eddie!think!harvard!seismo!brl-sem!brl-smoke!smoke!gwyn@BRL.ARPA
From: gwyn@BRL.ARPA (VLD/VMB)
Newsgroups: net.lang.c
Subject: Re:  questions from using lint
Message-ID: <464@brl-smoke.ARPA>
Date: Thu, 1-May-86 07:38:28 EDT
Article-I.D.: brl-smok.464
Posted: Thu May  1 07:38:28 1986
Date-Received: Sun, 4-May-86 06:40:33 EDT
Sender: news@brl-smoke.ARPA
Lines: 15

Re: "lint" not being as smart as Root Boy Jim

That's really silly.  I write C code such that I expect absolutely
NO warnings from "lint" (except for malloc pointer type-cast, which
is unavoidable at present); then if I get any "lint" warnings, they
indicate BUGS that must be fixed.  This is tremendously helpful.

I find that there are very few "inherently nonportable" applications.
Even when an application is designed to use specific hardware,
portable programming techniques contribute to better code quality.

Lint-free coding comes naturally after a bit of practice.  I find
it no burden at all, and hardly have to think about it.  Indeed,
it helps organize my use of complicated data types so that I get
the code right (and portable!) the first time.