Re: Weeding out unwanted include files

Gary Funck writes
> 1) run mkdepnd to derive the list of header files that a given source
> file depends on.
>
> 2) iteratively remove the #include of each file mentioned in mkdepend
> list. If the file still compiles, leave that #include out, and
> continue to iterate. Otherwise, add the #include back in and
> try removing the next mentioned header file, and continue to iterate.
>
> This method probably works best if you use a strict ANSI compiler
> that will complain if the prototype for a gaiven routine definition
> is missing. You may have to consider type mismatch warnings as
> "fatal" also.
>
> This method won't give an optimal arrangement of #includes, but
> may at least give a simple method for removing unwanted #include files.


In the following, is the include of foo.h in foo.c "required?" (Lest you
think I'm nitpicking, such situations exist in the project I'm working on
now. I consider at least one of them a bug, but not all code in the world is
well written.)


-----Contents of foo.h-----
#define foo "foo"
-----Contents of bar.h-----
#ifndef foo
#define foo "bar"
#endif


/* Make bar.h definitely required. */
#define output_function puts
-----Contents of foo.c-----
#include <stdio.h>
#include "foo.h"
#include "bar.h"


int main(void)
{
output_function(foo);
exit(0);
}
--
Zalman Stern zalman@adobe.com (415) 962 3824
Adobe Systems, 1585 Charleston Rd., POB 7900, Mountain View, CA 94039-7900
--

Return to the comp.compilers page.
Search the comp.compilers archives again.