Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site brl-tgr.ARPA
Path: utzoo!watmath!clyde!burl!ulysses!allegra!mit-eddie!godot!harvard!seismo!brl-tgr!tgr!gwyn@Brl-Vld.ARPA
From: Doug Gwyn (VLD/VMB) <gwyn@Brl-Vld.ARPA>
Newsgroups: net.lang.c
Subject: Re:  SIZEOF
Message-ID: <7810@brl-tgr.ARPA>
Date: Tue, 29-Jan-85 11:05:01 EST
Article-I.D.: brl-tgr.7810
Posted: Tue Jan 29 11:05:01 1985
Date-Received: Wed, 30-Jan-85 19:06:08 EST
Sender: news@brl-tgr.ARPA
Organization: Ballistic Research Lab
Lines: 5

"lint" is invaluable and we use it frequently in our application
development work.  It picks up many common mistakes, some of which
are unintentional and some of which are due to misunderstandings.
The rule in my team is "make the code pass lint completely or else
explain why it can't possibly".