Code analyzer found thousands of bugs in SE

More than a year ago, there was an article about SE check with static code analyzer ( https://www.viva64.com/en/b/0376/ ). It's results were:
75 important,
92 medium,
817 unimportant warnings/errors.

After around a month, I made the same check with newer SE source code (Feb 2016 end), here's the result:
92 important warnings,
152 medium,
874 small warnings/errors.

We can see error growth.

And now...(drumroll)... game check from 06.01.2017 (last source-code update on Github):
350 (LOOL) important,
748 medium,
1063 small warnings/errors...

It seems that bugfixing is going wrong...

Here's proof of last check:

 

Clearly this is an invalid system to check the SE code with, as it is called "static code analyzer" and the SE code is dynamic, as it changes at least once a week

 

When the QA department drank too much beer

 

These are not bugs, these are scheduled features

 

Static analysis doesn't always show bugs, but more like improper coding techniques, or failures to clean up due to changing code.
Yes it can reveal bugs, but not always. Some of them, like the 'comparison is never true' could simply be dead code which really should just be removed.
I'm sure that'll eventually get cleaned up, but static analysis has to be manually run, it's not something the compiler just does. Which means they don't show up during builds, and are less visible.

For example, naming a constant in ALL_CAPS, as is standard in C, is flagged in C#, and Keen does that. That's not a bug, just a break in C# coding standards.

 

So you're running a tool against GitHub code that's 3 months out of date and is so gimped it doesn't compile for legal reasons, and you're trying to say that compiler warnings in that mean the game is getting buggier? Lul.

 

To summarize this thread, there are bugs in the game, and there has been a ton of code added in the last few months.

In other news, grass is green, water is wet, and this thread is closed.