[cfe-dev] Finding redundant #includes
kremenek at apple.com
Sat Dec 12 11:56:40 PST 2009
Doing it correctly wouldn't be too hard from the AST perspective, but would be tricky when considering preprocessor logic. Any macros defined in a header and later used outside that header causes a dependency. Moreover, if a file can be compiled under different contexts, e.g., on Mac OS X one can compile for i386, x86_64, etc., then the "liveness" of a #include can change between translations.
On Dec 12, 2009, at 8:51 AM, steve naroff wrote:
> Hi Andrew,
> I don't believe we currently have such a feature (though it's an
> interesting idea).
> Implementing this wouldn't be too difficult, however it certainly
> isn't a "quick hack".
> On Dec 12, 2009, at 11:13 AM, Andrew Price wrote:
>> Can clang's analysis features help me find #includes which are no
>> required in a C source file? I'm working on cleaning up some old
>> code and it would be good to have this functionality.
>> cfe-dev mailing list
>> cfe-dev at cs.uiuc.edu
> cfe-dev mailing list
> cfe-dev at cs.uiuc.edu
More information about the cfe-dev