Code review comment for lp:~widelands-dev/widelands/codecheck

> Nice intiative :)

Thanks, but this also scratches two concrete itches I had:
1) I added a new lint in another branch and found out that you cannot reliably run the lint tests anymore because some fail.
2) Errors in the docs trigger an email per hour that ends up in my inbox. There are currently errors in the docs and I'd like the email flood to stop.

cppcheck is orthogonal to these things - but I agree that it would be useful.

And yes, errors in the docs and in the lint testsuite will now break the build.