Is it possible that cppcheck is not C++11 ready?
Static source code analysis tool for C and C++ code
Brought to you by:
danielmarjamaki
Menu
▾
▴
I've recently done some serious refactoring on an existing project that was written pre-C++11. In my rewrite I made heavy use of C++11-features such as range-based-for, lambdas, trailing return types, etc, etc.
The code compiles just fine on GCC 4.9.1, and testing has shown that it works as expected.
Letting cppcheck have a go at my code results in it giving exactly one error in lots of files, namely a "syntax error" in some random code line that contains no syntax errors whatsoever.
There are also tons of warnings about data members not being initialized in the constructor, when I clearly used delegating constructors to defer the initialization to another overload of the constructor, something that cppcheck doesn't seem to recognize.
All this leads me to suspect that cppcheck doesn't properly support C++11 yet.
yes, I think so.
but I don't think the situation is hopeless.
feel free to open some tickets if you can create short code examples that don't work.
Hi. Any chance cppcheck will learn to deal with C++11/14 code any time soon? Version 1.74 still poops out on every single one of my .cpp files. :-(
We are making progress on C++11 and C++14. For example, C++14 digit separator support has improved since the release of 1.74. Which features that cppcheck does not support are you using and which of them is causing the trouble?
I'm not 100% sure which feature it is, but since I'm getting that error for every single file and the one common feature I'm using everywhere is trailing return types, I'm guessing that's what's causing the problem.
Trailing return types is a feature that we do not support yet. I have started to implement it now. See also http://trac.cppcheck.net/ticket/4348
This commit adds support for trailing return types:
https://github.com/danmar/cppcheck/commit/801fd8f96aafce772f367f3ace9e839a77e81723
Fantastic! :) Thanks a bunch for your work!