![]() Talking about how many nuances get in the way. And what's interesting, we managed to run the PVS-Studio on Linux on the very first day of working on the task! Yet the PVS-Studio analyzer for C# for Linux/macOS release was shipped only six months later. Hello from the C# department! About a year ago we ported the C# analyzer on Linux and macOS. What if there's not much to finish? Surprisingly, the code compiled immediately and that cheered us up. Either we modify the existing prototype, or start all over again.Īfter we found the sources in the repository, we decided to check the level of its readiness. More precisely, we had a couple of possible ways. Now, since the users became more and more interested, we decided to finish what we've started. ![]() But it was not destined to finish it for a number of reasons. Yes, some time ago we started developing it. Truth be told, we had a plugin prototype for CLion. Imagine what would happen if we also added the compiler's warnings. ![]() Note that PVS-Studio has an incremental analysis – the mode that checks only the changed files.Īs a result, the CLion analysis and PVS-Studio analysis complete each other. PVS-Studio doesn't highlight errors immediately, but it can perform deeper analysis. CLion highlights the errors on the fly, but at the same time is limited in the analysis capabilities. Here's an answer to the question that we are discussing - PVS-Studio and CLion collaboration will let us detect more errors at the writing code stage. Consider inspecting operation logics behind the 'buffer' variable. V611 The memory was allocated using 'new' operator but was released using the 'free' function.V522 There might be dereferencing of a potential null pointer 'buffer'.PVS-Studio, however, issues two warnings:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |