Topic: How to use PVS-Studio it is free
We want to help to get acquainted better to the world of the software with tools of static analysis of the code and to raise quality of the software. We give possibility of free usage of analyzer PVS-Studio to students in the educational purposes, to individual developers and collectives of enthusiasts. Introduction by Clients of analyzer PVS-Studio departments of developers of the various companies are. We would like, that individual developers were our clients also. Unfortunately, at us it turned out nothing with the experimental product CppCat. We do not know how to construct successful business in sphere of static analysis of the code, selling personal licenses. Therefore now product PVS-Studio is positioned exceptional as B2B the decision. I think that our dip with CppCat has been predetermined. The world dictates the laws, and, for example, the same Coverity is oriented on corporate licenses. However, it does not mean that it is necessary to eliminate other variants of interaction with the world. We long thought how to help small design teams or how to spread the academic licenses. At first sight it seems that the most simple way - to give licenses to those who develops the free software. Unfortunately, this decision not seems to us to correct. It is necessary to explain our position. However, if you would like, you can pass at once to section "Free license PVS-Studio". If to the reader is interesting to receive particulars I suggest to continue reading. Speculations we Present the individual developer developing and selling, for example, any game. Its code is closed and used in commercial objectives. Nevertheless, we are glad to help it to get acquainted with methodology of static analysis of the code and are ready to present to it the license. It is an advertizing step which can pay off in due course. Now it one but who knows that happens in 5 years. On the other hand, we take a command from 50 persons who are working in the large company and engaged in creation of the open free project. 50 persons at office sit, eat cookies, get wages and thus position itself as idealists in the plan for development of the free software. Yes, the product is free, but the company derives from its existence the considerable profit indirect methods. Simply for some reasons it is convenient the company, that the project was opened and free. It seems to us quite fair that such organization should acquire the paid license for analyzer usage. As you can see, the criterion programs or opennesses of the code does not approach us for decision-making. It would be desirable to divide the projects developed in the company, and projects of small collectives of enthusiasts. It is possible to make it exceptional software license agreement, but in that case it is difficult to lead boundary between different types of projects. In addition, it helps us from the point of view of advertizing a little. Let's be fair: the companies give free licenses for the sake of advertizing. In it we are not worse and it is not better than others. The decision has been found intuitively. What distinguishes corporate projects from projects of enthusiasts? In corporate projects there is less than freedom and more bureaucracy. Hardly the Microsoft company management will be glad, if the developer in Microsoft Office code writes that it is its personal project. These should to use and suggest import to the editing code in which it is mentioned PVS-Studio. At the same time the code of open projects will advertize PVS-Studio. Free license PVS-Studio you need to fulfill two steps to start to use free of charge static analyzer PVS-Studio. A step 1. If you use PVS-Studio as a plug-in to a Visual Studio enter the following license key: Name: PVS-Studio Free Key: FREE-FREE-FREE-FREE If you use PVS-Studio for Linux at once pass to the second step, the file with the license is not required to you. A step 2. Import editings to all compiled files of your project. Files with c extensions, cc, cpp, cs and so on Mean. It is not required to change heading h-files. You should inscribe in the beginning of each file two lines with the comment. We give some variants on a choice. It some kind of a board for possibility of free usage of analyzer PVS-Studio. Comments for students (the academic license)://This is a personal academic project. Dear PVS-Studio, please check it.//PVS-Studio Static Code Analyzer for a C, a C ++ and C#: http://www.viva64.com Comments for open free projects://This is an open source non-commercial project. Dear PVS-Studio, please check it.//PVS-Studio Static Code Analyzer for a C, a C ++ and C#: http://www.viva64.com Comments for individual developers: //This is an independent project of an individual developer. Dear PVS-Studio, please check it.//PVS-Studio Static Code Analyzer for a C, a C ++ and C#: http://www.viva64.com it is finite, the offered variants approach not all. In it their sense also consists. If any of the offered variants does not approach you, suggested to consider with us a question of purchase of the license. The remark. Besides the method of free usage of the analyzer described here, you can download still from a site the demonstration version of the analyzer for acquaintance. If you want to remove for a while restrictions of the demonstration version we ask to write to us. Automation If in your project is a lot of files you can use the auxiliary utility. You should specify it what comment to interpose and the directory with the code. Then the utility recursively bypasses all files in a folder and nested folders, adding in files with the source code appropriate comments. To download the utility (together with the source code) it is possible here: how-to-use-pvs-studio-free. The inference Some developers can tell that two lines with the comment which is not concerning an essence the project do not want to see in the beginning of a file. Their this right, and they can simply not use the analyzer. Or they can acquire the commercial license and use it without restrictions. We consider presence of these comments, as gratitude for the given license and, at the same time, as additional advertizing of our product. I think, it is a good, fair exchange. At the same time the question of separation of corporate projects from private initiatives is solved. If the project is done by enthusiasts, they in the right to do with the code everything that would be desirable them including to add such comments. If is not present, means behind the project there is a certain organization from which we want to obtain reward in the form of license acquisition. We hope our sentence and a position are clear. If you still have questions we ask to write to us. To convince your colleagues to start to use the analyzer of code PVS-Studio, we suggest to acquaint them with following sections of our site: the Errors which have been found out in Open Source projects by means of PVS-Studio of Article in which we tell about the found errors of Thanks for attention. Let's make together programs more reliably and more safely. Addition Arose many reasonings on a subject of, whether is admissible to add and delete comments in the source code free of charge to use the analyzer. We consider such reception unacceptable as it upon is a method of bypass of the restriction superimposed by us on the free license. Therefore we decided to add the following section in the software license agreement: you have the right to use PVS-Studio free of charge, adding in the source code of the project comments of a special type. Which comments should be added and how to automate this process it is described in article "How to use PVS-Studio free of charge". We mark that the given mode is not intended for an estimation of possibilities of the analyzer. To get acquainted with the analyzer, you should use the demonstration version or request of us a temporary license key. You should interpose comments when you already decided that will use the analyzer on the regular basis. You can delete these comments in a consequence, but can make it only once. Repeated adding of comments in the source code with their subsequent removal is not admitted. Also repeated adding of comments with the subsequent rollback of contents of source files by means of the monitoring system of versions is not admitted. Such actions are directed on condition bypass that the source code should contain comments, and are violation of the given agreement on analyzer usage.