> If we had a static analyzer that ran automatically as part of the WebKit > development process, and a shared goal to get its complaints down to 0, > then it might be reasonable to skip creating tests for issues that it > diagnoses. But that doesn't seem to be the situation here. >
If we ran a static analyzer as part of the process with the goal of having cleaner code, we could have demonstrably avoided at least one bug with a big enough impact to avoid a hot patch. Mind, I'm not advocating doing that. I'm aware that false positives and a lot of "noise" bugs make this a very difficult goal to achieve. What we currently do strikes me as the better approach - we run the analyzer, and people who actually care about that kind of stuff triage and fix the remaining actual issues. (And believe me, we triage out quite a bit :) Rachel
_______________________________________________ webkit-dev mailing list [email protected] http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
