Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!auspex!guy
From: guy@auspex.auspex.com (Guy Harris)
Newsgroups: comp.unix.misc
Subject: Re: Human-readable lint libraries
Message-ID: <4212@auspex.auspex.com>
Date: 30 Oct 90 23:51:59 GMT
References: <1990Oct19.172042.26917@batcomputer.tn.cornell.edu> <MUTCHLER.90Oct19132818@zule.EBay.Sun.COM>
Organization: Auspex Systems, Santa Clara
Lines: 23


 >   However, there are no flags (or combinations of same) which
 >   seem to result in the production of said "stripped down lint
 >   library source files".

...

 >From the lint manual page:
 >
 >	-Clibrary
 >		Create a lint library with the name llib-llibrary.ln.
 >
 >Also, -i will generate a .ln file with just the routines and the call
 >lines.

Nice try, but a ".ln" file is *NOT* a "stripped down lint library source
file", it's a *binary* "lint" library file.  As Larry McVoy (who was
recently in hand-to-hand combat with "lint" libraries) notes, having the
stripped-down source files are handy, because when "lint" complains
about a parameter mismatch between line XXX of YYY.c and line NNN of
llib-ZZZ, you can go look at line NNN of llib-ZZZ (that being the
stripped-down "lint" library source file) and see what parameters the
routine expects.