I have a hankering to try to use dxr to evaluate a body of software for things like:
1. unused #include (i.e., stuff from that #include isn't ever used in that source file) 2. unnecessary #include (i.e., types from the #include could be used with a forward decl rather than full decl) 3. lazy #include (type used, but neither #include'd nor forward decl'd) Obviously, doing this requires that include files be tracked. Does dxr do that? If not, could it, i.e., does the plugin model for clang provide hooks for capturing that information, or is that all done too far upstream? -- Chris Cleeland _______________________________________________ dev-static-analysis mailing list [email protected] https://lists.mozilla.org/listinfo/dev-static-analysis
