James Carlson writes: > You need to get lint's flow tracing engaged. I usually use > "-Nlevel=2" to do this, but beware that you'll get way more output > than you might want. (On the plus side, that mode identifies unused > include files, so it's a good thing to do even if you ignore much of > the output.)
It's also useful to know that when any "-Nlevel" option is used, lint actually runs a completely different program -- it execs prod/bin/lint2n (the "new" lint) instead of prod/bin/lint2 (the "old" lint). As it's a different implementation, it tends to behave differently in some cases. The bulk of the ON code base has been designed for 'lint2'. It'd be nice to make it work as well with lint2n, but I don't think anyone's doing that yet. -- James Carlson, Solaris Networking <james.d.carlson at sun.com> Sun Microsystems / 35 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677
