Oliver Stöneberg
Oliver Stöneberg
I adjusted the messages but added a bunch of TODOs.
Having an unknown mail address is probably not good. So maybe we should not use that field.
Still work in progress... The standard library and LLVM are specifying this among others. Just running it on `/usr/include` will encounter lots of actual usages. This will be disabled by...
Requires #6325 to be merged first. After #6211 has landed (if even possible) and we finally upgraded to PCRE2 (see https://trac.cppcheck.net/ticket/10610) we should replace most of the messy parsing code...
> What is the canonical use case for this? That is described in the ticket. It is mainly for IDE integrations. When you open a header by default it will...
> Thanks for the explanation. IDEs were mentioned in the ticket, but I didn't make the connection to IDE integration. I just realized there is no upstream ticket for this....
I also encountered some performance issues with some headers even when I disable ValueFlow and all checks so it is probably related to the tokenizing or preprocessing. I have not...
> I also encountered some performance issues with some headers even when I disable ValueFlow and all checks so it is probably related to the tokenizing or preprocessing. I have...
To test this with existing headers I patched out some code for speed, enabled the logging in `hasEmacsCppMarker()` and ran `find /usr/include -type f | xargs -n 1 bin/cppcheck -D__GNUC__...
This does not currently handle markers in `/* */` comments. I will add support for that in a follow-up PR.