Oliver Stöneberg

> It is the `mTokenizer->hasIfdef()` call in `CheckClass::checkConstFunc()`. I filed some tickets about possible improvements in the handling: https://trac.cppcheck.net/ticket/13740 https://trac.cppcheck.net/ticket/13741

Superseded by #7415.

Might make sense to be able to specify the type via a rule file as well. That would also allow to mix and match the engines depending on required performance/features....

This will only add the additional engine. I will also do some performance tests. The follow-up steps are: - implement PCRE2 as an additional engine and make it optional via...

> Might make sense to be able to specify the type via a rule file as well. That would also allow to mix and match the engines depending on required...

No comment so I will go with the way to specify the engine via XML only and not providing a CLI option for it.

> The follow-up steps are: I filed some tickets for those: https://trac.cppcheck.net/ticket/14262 https://trac.cppcheck.net/ticket/14263

The documentation on how to use rules is unfortunately some PDFs hosted at Sourceforge so there is nowhere to add the new field. I filed https://trac.cppcheck.net/ticket/14264 about migrating the documentation.

Great - `std::regex` appears to behave differently in Visual Studio: ``` D:\a\cppcheck\cppcheck\test\testregex.cpp:181(TestRegExStd::exactmatch): Assertion failed. Expected: 0 Actual: 2 ``` Why am I not surprised?! And on macos `testrunner` is not...

> Great - `std::regex` appears to behave differently in Visual Studio: Apparently `std::regex` is partially broken in the current Visual Studio version (not sure if it is what affects the...