On 09/27/2011 01:24 PM, Noel Grandin wrote:
(1) Nice pragma trick for making this problem show up at compile time: http://stackoverflow.com/questions/74326/how-should-i-detect-unnecessary-include-files-in-a-large-c-project/109890#109890
This would flag double includes that are there for good encapsulation, like when a header contains an inline function definition using rtl::OUString (so header #inlcude "rtl/ustring.hxx"), and that header is included in a cxx that also contains a function definition using rtl::OUString (so cxx too #include "rtl/ustring.hxx").
(2) There is a tool based on clang that can detect unused includes: http://code.google.com/p/include-what-you-use/
Cool, thanks for the pointer. Always thought about doing something like this, but never came around...
-Stephan _______________________________________________ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
