Re:John Carmack on Static Code Analysis
by johnyzee on Wednesday September 19, 2012 @03:45PM
(#4545204)
What do they give you that you don't get with open source tools like Clover, Findbugs and Checkstyle?
Re:John Carmack on Static Code Analysis
by timtadh on Wednesday September 19, 2012 @06:41PM
(#4545929)
Accuracy. Detail. They have better analysis engines, which do more complex types of program analysis. The static program analysis field is incredibly deep it takes a lot of engineering to make a world class analysis engine. Just like it takes a lot of effort to make a world class optimising complier. (eg. the Intel C Compiler still out performs GCC despite monumental effort on GCC's side. It takes a long time to build this stuff)
They also have better rules sets from what I understand than the open source tools.
While the Intel compiler may be better in some/many cases, it is not universal. In my experience (a couple of years ago, C++ code, high-performance requirements), the Intel compiler was quite a bit worse than GCC for code with a lot of branches and abstraction layers.
The Microsoft compiler was way better than both. Around 10% faster run-time IIRC.
Re:John Carmack on Static Code Analysis
by raverbashing on Thursday September 20, 2012 @04:33AM
(#4547638)
What are the main issues with Java code that these tools find?
Both produce high quality output in their domain. Fortify is widely use in the AppSec world.