Feb 5, 2020
A static code review does not need the execution of the code while a dynamic code analysis is mainly dependent on how well the code performs.
seen from United States
seen from T1
seen from Belgium
seen from United States
seen from United States
seen from United States
seen from Uruguay
seen from Indonesia
seen from China
seen from Sweden
seen from Hong Kong SAR China
seen from Singapore
seen from Thailand
seen from France
seen from Germany
seen from United States
seen from Switzerland
seen from France
seen from Yemen
seen from Indonesia
A static code review does not need the execution of the code while a dynamic code analysis is mainly dependent on how well the code performs.
This just sounds super fucking useful. Great work coming out of Google.
As a PVS-Studio's developer, I am often asked to implement various new diagnostics in our tool. Many of these requests are based on users' experience of working with dynamic code analyzers, for example Valgrind. Unfortunately, it is usually impossible or hardly possible for us to implement such diagnostics. In this article, I'm going to explain briefly why static code analyzers cannot do what dynamic analyzers can and vice versa. Each of these analysis methodologies has its own pros and cons; and one cannot replace the other, but they do complement each other very well.