> Sorry, I meant improving the ClangDiagPathDiagConsumer to print the checker names (probably controlled by > an -analyzer-config option, but possibly even on by default). The checker hierarchy is not a wonderful long- > term solution, but it's what we've got, even for people using scan-build.
The problem is, that we not only need the checker name as a part of the message (which is a nice side-effect), but as a separate piece of data, and I wouldn't like to parse it out of the message. http://llvm-reviews.chandlerc.com/D2556 _______________________________________________ cfe-commits mailing list [email protected] http://lists.cs.uiuc.edu/mailman/listinfo/cfe-commits
