Oliver Stöneberg
Oliver Stöneberg
Coincidentally Visual Studio 2026 was released just a few hours ago and I can confirm that the test passes in it.
Requires #7918 to be merged first. And also needs a test added for the replaced code in `CppCheck::checkInternal()`.
This is also in preparation of https://github.com/danmar/simplecpp/pull/573.
Still fails tests because as inline suppressions are now being tracked globally until the end of the analysis ones that are found in included filed might be picked up more...
> Still fails tests because as inline suppressions are now being tracked globally until the end of the analysis ones that are found in included filed might be picked up...
In a future version Clang will add a warning suggesting adding such annotations. These have been placed by simplify reviewing the code.
``` /home/user/CLionProjects/cppcheck/test/testcmdlineparser.cpp:134(TestCmdlineParser::versionWithInvalidCfg): Assertion failed. Unexpected exception was thrown: ScopedFile(/home/user/CLionProjects/cppcheck/cmake-build-debug-clang/bin/cppcheck.cfg) - file not unique _____ /home/user/CLionProjects/cppcheck/test/testcmdlineparser.cpp:286(TestCmdlineParser::suppressions): Assertion failed. Unexpected exception was thrown: ScopedFile(suppr.txt) - file not unique _____ /home/user/CLionProjects/cppcheck/test/testcmdlineparser.cpp:325(TestCmdlineParser::errorlistWithCfg): Assertion failed....
The way we currently run our tests, conflicts within the same fixture cannot happen. So not everything raised by this check might actually be causing issues.
> The way we currently run our tests, conflicts within the same fixture cannot happen. This would allow us to register each test individually - see https://trac.cppcheck.net/ticket/14114.
Requires #7860 to be merged first.