Identifying unnecessary #includes

Casey Link unnamedrambler at
Sun Mar 28 00:55:39 UTC 2010

> The needed information is avaliable in DUChain, it's just a matter of using it.
> The easiest way would be to write a plugin that does the #include-cleanup for
> the currently open file - that way you can easily review the changes.
> Or would you prefer to execute this action for all files at once?

Ideally, we would like to execute this action over many files at once
(a directory and its subdirs). The ability to see the symbols each
include file provides (that are used) and the option to remove unused
ones would be great features.


More information about the KDevelop-devel mailing list