Xref: utzoo comp.bugs.sys5:696 comp.unix.questions:10255
Path: utzoo!attcan!uunet!ncrlnk!ncr-sd!hp-sdd!hplabs!decwrl!purdue!mailrus!ncar!boulder!spot!wu
From: wu@spot.Colorado.EDU (WU SHI-KUEI)
Newsgroups: comp.bugs.sys5,comp.unix.questions
Subject: Re: lint pass2 error
Message-ID: <4717@boulder.Colorado.EDU>
Date: 17 Nov 88 16:31:17 GMT
References: <173@isncr.is.se>
Sender: news@boulder.Colorado.EDU
Reply-To: wu@spot.Colorado.EDU (WU SHI-KUEI)
Organization: University of Colorado, Boulder
Lines: 25

In article <173@isncr.is.se> ra@isncr.is.se (Robert Andersson) writes:
. . .
>The program in question is some 20,000 lines, spread out over ~100 files and
>~500 functions. It obviously overflows some internal lint buffer.
>Exactly what does the error message mean, and is there a way around it,
>like some 'undocumented' lint option or whatever?

I am not sure that this will help, but on our SVR2 AT&T 3B, running the 3.1
release of the compiler, lint has a -c option which allows you to run lint
on each of the source files individual source files.  Only the first pass 
is executed, with no checks for inter-function compatibility, and the
output is left in *.ln files.

Then, execute 'lint *.ln', which runs the remaining passes upon the
package as a whole.  One would hope that the *.ln files contain only data
needed to check inter-function compatibility, thus reducing the number of
names the second pass must deal with.

Incidentally, this is a neat feature to use with 'make' - individual source
files can be linted as they are created and then the whole shebang tested
for overall compatibility.

Hope this helps - In real life:
Carl Brandauer
{uunet|stcvax}!nbires!bdaemon!carl