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!linus!philabs!cmcl2!seismo!brl-tgr!gwyn
From: gwyn@brl-tgr.ARPA (Doug Gwyn <gwyn>)
Newsgroups: net.lang.c
Subject: Re: 6 char externs and the ANSI standard
Message-ID: <5742@brl-tgr.ARPA>
Date: Tue, 13-Nov-84 11:31:19 EST
Article-I.D.: brl-tgr.5742
Posted: Tue Nov 13 11:31:19 1984
Date-Received: Thu, 15-Nov-84 01:53:08 EST
References: <13241@sri-arpa.UUCP> <270@ukma.UUCP>
Organization: Ballistic Research Lab
Lines: 15

> Who actually uses lint?  ...
> 
> I am actually curious how useful it is.  ...

I have made a practice of writing C code that passes entirely
unscathed through "lint" (SVR2 version) and find that it helps
tremendously when I have accidentally omitted an & from a struct
paramater to a function or some other hard-to-find mistake.
Often when someone brings me buggy code to help with, "lint"
shows their problem.  This is quite apart from its use in making
one's code portable.

The only thing I have not been able to keep "lint" happy about
is the use of a pointer returned by malloc() for some non-(char *)
datum.  This problem should go away with the advent of (void *).