Lars Gullik Bjønnes wrote:
> Angus Leeming <[EMAIL PROTECTED]> writes:
>
> | <shrug> Why? But ok: </shrug>
>
> Not just for this test, but if we have situation where something
> flagged really shouldn't be.
>
>>> Sure, I think you have caught all cases. What this "make test" would
>>> be for is _new_ changes to CVS, so that we catch "regression" like
>>> this early.
>>
> | Sounds a little officious to me ;-)
>
> A lot better to catch it before commit than having to do the stuff you
> have done now ..
>
> | You _really_ don't want to do that. To test for redundant #includes in the
> | src directory alone took 41 minutes on my 2.7GHz machine here...
>
> separate make target then.
Why?
Why not take the script I posted last night (check_strip.sh),
replace the line
mv -f ${TESTFILE} ${INPUTFILE}
with
echo ${LINE} of ${INPUTFILE} may well be redundant. Please investigate.
and just run it. Preferably overnight.
$ find . -name "*.[Ch]" | xargs check_strip.sh includes > redundant_includes.txt
$ find . -name "*.[Ch]" | xargs check_strip.sh using > redundant_using.txt
All you need to do is add those three scripts to the development
directory somewhere.
--
