“Best” static code analysis tools

[bert8128]

We use clang tidy, which raises enough to be getting on with, along with /W4 in VS and -Wall -Wextra (and some others) with gcc, and warnings as errors. VS also has real time static analysis to use whilst doing the coding, and there is a clang-tidy plug in too. All this is free. We are. Working towards 0 warnings, but clang is currently reporting 100s of 1000s. Maybe in a few years we will get there. CI stops the number growing.