This paper contains some questions and answers about VivaCore C/C++ code analysis library by OOO "Program Verification Systems"
VivaCore is an open source library for working with C and C++ code. The library is an open design with an open source written in C++. VivaCore is based on OpenC++ library (OpenCxx). One should not mix up VivaCore and some professional multifunctional parsers of C and C++ code. If a user needs a front-end code parser supporting the modern standard of C++ and allowing to create its own compiler within a specific platform, he should regard GCC or some expensive commercial solutions.
The following improvements are added to VivaCore:
VivaCore can awake interest of companies and enterprises planning or developing tools for work with a code. Applications in the following fields may be developed by means of VivaCore:
VivaCore library is developed by OOO "Program Verification Systems". VivaCore license gives you enough freedom to use, copy, spread and modify it in binary form or as a source code for both commercial and non-commercial use without any royalties. The only thing you need is to specify the authors of the source libraries (OpenC++ and VivaCore).
On the one hand, C++ analysis library is meant for code analyzing without paying attention to specific character of any operation system or software platform. But on the other hand, VivaCore is represented as design for Visual Studio 2010, so the easiest way to fit it out is to do it in Windows environment. Please note that both full and express versions of Visual Studio 2010 are able to be used for build.
Yes, we are.
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 ...
Many programmers think that the more error messages a static code analyzer produces, the better. It would be true if all the messages hit the bull's eye, as they say. But this is impossible: the same warnings may be considered both true and false by different programmers depending on the project type. There is also one more important and interesting ...