That's why if you happen to read this article in a month or more from the moment of its publication, I advise installing a current version of the distribution: With time this link will become a dead one. So, if you are interested, I suggest downloading the current version of the experimental variant of PVS-Studio by this link. Adding new diagnostics is a quick process. It is important for us to make sure that we are moving in the right direction and that the analyzer is runnable in general. We'll be really grateful to anyone who would do that. But you can already install and try this version now. At this point there are few diagnostics in it (at the moment of writing of this article, there were 36 of them). I should warn that the full version of PVS-Studio analyzer is not ready yet. To our own humble opinion, we'll be able to create a very useful tool that many C# developers can benefit from.Īnd now our main task is to start getting feedback from our potential users as soon as possible. Time will tell if it is going to be a successful affair. So we decided to try applying our experience to another programming language, namely C#. it doesn't matter which language you use, as there will always be typos and errors due to carelessness or Copy-Paste usage. In the course of time we realized that a big number of diagnostics is not related to a particular programming language, i.e. We've implemented a great deal of interesting and unique ideas on bug detection. We have successfully created PVS-Studio analyzer for C/C++ languages and continue developing it. I'll try to come up with a decent answer for us and our potential clients, as we need to have a clear understanding of where and why we are going. Now one of the most important questions for us is: "Why should we make another analysis tool for C# in general?"
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |