{"id":91065,"date":"2020-08-08T01:42:18","date_gmt":"2020-08-07T23:42:18","guid":{"rendered":"https:\/\/prohoster.info\/blog\/administrirovanie\/staticheskij-analiz-ot-znakomstva-do-integraczii"},"modified":"2020-08-08T01:42:18","modified_gmt":"2020-08-07T23:42:18","slug":"staticheskij-analiz-ot-znakomstva-do-integraczii","status":"publish","type":"post","link":"https:\/\/prohoster.info\/en\/blog\/administrirovanie\/staticheskij-analiz-ot-znakomstva-do-integraczii","title":{"rendered":"Static analysis \u2013 from introduction to integration","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

Tired of endless code reviews or debugging, you sometimes wonder how to make your life easier. With a bit of searching, or perhaps by chance, you might come across the magical phrase: \"Static Analysis\". Let\u2019s explore what it is and how it can interact with your project.<\/p>\n

\"Static<\/a><\/noindex>
\nActually, if you're programming in any modern language, you've unknowingly been passing your code through a static analyzer. The thing is, every modern compiler provides at least a few warnings about potential issues in the code. For example, when compiling C++ code in Visual Studio, you might see the following:<\/p>\n

\"Static
\nIn this output, we can see that the variable var<\/i> was never used anywhere in the function. So in fact, you\u2019ve almost always been using a simple static code analyzer. However, unlike professional analyzers like Coverity, Klocwork, or PVS-Studio, the warnings provided by the compiler can only indicate a small range of problems.<\/p>\n

If you're not sure what static analysis is and how to implement it, read this article<\/a><\/noindex>, to get a more detailed understanding of this methodology. <\/p>\n

Why is static analysis needed?<\/h2>\n

\nIn short: to speed things up and simplify them. <\/p>\n

Static analysis can uncover a variety of problems in the code, from incorrect use of language constructs to typographical errors. For example, instead of <\/p>\n

auto x = obj.x;\nauto y = obj.y;\nauto z = obj.z;<\/code><\/pre>\n
\nyou wrote the following code:<\/p>\n
auto x = obj.x;\nauto y = obj.y;\nauto z = obj.x;<\/code><\/pre>\n
\nAs you can see, there\u2019s a typo in the last line. For example, PVS-Studio gives the following warning:<\/p>\n
V537<\/a><\/noindex> Consider reviewing the correctness of 'y' item's usage.<\/p>\n
If you want to poke at this error hands-on, try the ready-made example on Compiler Explorer: *click<\/a><\/noindex>*.<\/p>\n
As you can imagine, it\u2019s not always possible to pay attention to such snippets of code right away, which can lead to spending a good hour debugging, wondering why everything works so strangely. <\/p>\n
However, this is a clear error. And what if a developer wrote suboptimal code because they forgot some nuance of the language? Or even introduced undefined behavior<\/a><\/noindex>? \u041a \u0441\u043e\u0436\u0430\u043b\u0435\u043d\u0438\u044e, \u043f\u043e\u0434\u043e\u0431\u043d\u044b\u0435 \u0441\u043b\u0443\u0447\u0430\u0438 \u0441\u043e\u0432\u0435\u0440\u0448\u0435\u043d\u043d\u043e \u043e\u0431\u044b\u0434\u0435\u043d\u043d\u044b \u0438 \u043b\u044c\u0432\u0438\u043d\u0430\u044f \u0447\u0430\u0441\u0442\u044c \u0432\u0440\u0435\u043c\u0435\u043d\u0438 \u0442\u0440\u0430\u0442\u0438\u0442\u0441\u044f \u043d\u0430 \u0442\u043e, \u0447\u0442\u043e\u0431\u044b \u043e\u0442\u043b\u0430\u0434\u0438\u0442\u044c \u0441\u043f\u0435\u0446\u0438\u0444\u0438\u0447\u043d\u043e \u0440\u0430\u0431\u043e\u0442\u0430\u044e\u0449\u0438\u0439 \u043a\u043e\u0434, \u043a\u043e\u0442\u043e\u0440\u044b\u0439 \u0441\u043e\u0434\u0435\u0440\u0436\u0438\u0442 \u043e\u043f\u0435\u0447\u0430\u0442\u043a\u0438, \u0442\u0438\u043f\u0438\u0447\u043d\u044b\u0435 \u043e\u0448\u0438\u0431\u043a\u0438 \u0438\u043b\u0438 undefined behavior.<\/p>\n
Static analysis has emerged specifically for these situations. It serves as a developer's assistant, pointing out various issues in the code and explaining in the documentation why certain coding practices should be avoided, what consequences they may lead to, and how to fix them. Here's an example of what it may look like: *click<\/a><\/noindex>*.<\/p>\n
You can find more interesting errors that the analyzer can detect in the following articles:<\/p>\n