Re: Weeding out unwanted include files

gary@Intrepid.COM (Gary Funck) writes:
>Well, the following method lacks elegance, but might give you the
>result you're after.


>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.


The problem is "compiles" and generates the correct code are different
things. In some cases header files remap function names to deal with
linkage conflicts or contain ifdefs that select a code variant depending
on the environment. If you remove one of these headers, you may get a
binary but it won't do you much good.


To support the full complexity of the C preprocessor requires a detailed
pass over the source - especially if you want the tool to examine the
contents of conditional compilation blocks.


Geoffrey Waigh
g9gwaigh@cdf.utoronto.ca
--

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