3 ms·
I guess the immediate question everyone has for such tools is how does it compare with clang-tidy for C++?
by ainar-g 9y ago
I guess the immediate question everyone has for such tools is how does it compare with clang-tidy for C++?
- bliker 9y agoClang tidy has more style related checks. Where oclint is better at diagnosing complexity. Saying that, I've recently felt like the development of clang tidy has been much more active and it will become the do-it-all tool very soon.
- dbaupp 9y agoAnd, similarly, what about vs. clang static-analyzer?
- bliker 9y agoClang static analyzer can be run as part of oclint run. It contains slower and more complex memory related checks.
- kennywinker 9y agoClang static analyzer is about checking logic errors - unused variables, memory leaks, etc. OCLint does things like warn if there are too many non-comment-lines-of-code in a method, or too many methods per class. It's more about keeping tabs on complexity and code cleanlyness than true static analysis. Ideally, use both! If you're using Xcode you can enable "analyze" for all builds. Highly recommended if it doesn't break your build times.
- ainar-g 9y agoIIRC, clang-tidy includes all clang-analyzer checks.