Oliver Stöneberg

> Isn't this going too extreme? Putting every function in a separate file. There are many small files that are less than 100 lines of code. This is just because...

> I would still say it's pretty extreme to put each function in a separate file. We could end up with 1000's of files if you continue to refactor cppcheck....

> splitting out each function into a separate file that is extreme to me. how about a file for all "non-analyzer" passes. this was always the plan from the beginning...

@pfultz2 please have a look. Thanks.

`-D __GNUC__ --check-level=exhaustive lib/utils.cpp` Clang 18 `851,620,331` -> `809,036,639` GCC 14 `880,259,918` -> `841,976,696` This should help with https://trac.cppcheck.net/ticket/12271. Detecting match calls in headers is tracked in https://trac.cppcheck.net/ticket/11541. This is...

The example from https://trac.cppcheck.net/ticket/10765#comment:4. Clang 17 `8,156,089,970` -> `7,669,984,764`

@pfultz2 Care to have a look at this? Thanks!

The example from https://trac.cppcheck.net/ticket/10765#comment:4. Clang 17 `3,753,065,367` -> `3,237,960,965` This makes a lot of difference and we really need to figure out how to get this change in properly.

I do not want the changes to go in this way but I am marking this for review so I hopefully get some more feedback on how to resolve this.

`-D __GNUC__ --check-level=exhaustive lib/utils.cpp` Clang 19 `699,175,113` -> `652,340,049` GCC 14 `744,553,244` -> `702,309,116` The example from https://trac.cppcheck.net/ticket/10765#comment:4. Clang 19 `3,624,176,882` -> `3,063,883,851` GCC 14 `3,884,644,414` -> `3,374,187,145` callgrind in...