We are pleased to be able to announce that the development of Visual Lint 3.0 is now nearing completion and it should be released by the end of March.
In preparation, since the start of the year our online store has been issuing licences compatible with both the latest version of Visual Lint 2.5 (184.108.40.206) and Visual Lint 3.0. As such, if you are intending to purchase full Visual Lint licences in the near future you do not need to worry about whether your licence might need to be upgraded soon afterwards - it won't!
Details of upgrades from other Visual Lint licences are now being finalised and will be published shortly; customers with active Priority Support subscriptions will of course receive new licences at no additional cost once the new version has been released.
Among the most visible changes in Visual Lint 3.0 are:
- Added a Visual Lint plug-in for Eclipse/CDT. This currently supports the analysis of managed builder projects but we will be adding makefile support in due course. If there are any particular Eclipse/CDT toolchains you would like us to support, please let us know.
- Added support for the CppCheck open source C++ analysis tool. Support for additional analysis tools such as the Google C++ style checker (cpplint) and the forthcoming new version of the ClockSharp C# code checker) is also likely to be added shortly.
- Added support for accelerated local PC-lint analysis tasks using PC-lint 9.0 precompiled header files. When enabled, Visual Lint will manage the PC-lint precompiled header object (
.lph) file for each project automatically, queueing other files in the project only once the .lph file has become available.
- Added code editor markers in implementation files and their corresponding primary header files in compatible versions of Visual Studio. When enabled, the appropriate category icon will be displayed in the gutter of the code editor on the line reported for each issue within the source file.
- Added an "Insert Directive" command to the Analysis Results Display context menu. When activated, the appropriate inline suppression directive (e.g.
//lint !e828) is inserted into the appropriate file within the code editor to suppress the selected issue in future analysis runs.
- When an analysis task starts on a file whose analysis results are currently shown in the Analysis Results Display, the existing results set will remain visible and greyed until the task starts to return new issues.
- The Analysis Results Display now allows the analysis results for any file within the solution to be manually selected. This also allows the analysis results for all files within a specified project to be simultaneously viewed within the same display.
- Visual Lint no longer requires the global PC-lint include configuration to be defined in std.lnt; instead
-i directives for the system include folders are automatically written to each project indirect (
project.lnt) file when it is updated.
- Analysis results can now optionally be stored in a user defined location rather than within the source tree of each solution.
Although this is not all of the headline items (we are still working on some fairly significant areas such as issue ID filtering and further display changes) it should be enough to give you an overview of the new version. Additional functionality will of course continue to be rolled out into subsequent 3.0 builds after the initial public release.
This is a major milestone in the development of Visual Lint, and one which reflects a change in emphasis from a pure Visual Studio based product supporting a single analysis tool (PC-lint) to one capable of fully supporting multiple environments and analysis tools. We're very proud of this version, and hope you will find it as much as a step forward as we do.
Finally, although preliminary builds of Visual Lint 3.0 have already been made available to our beta testers and Priority Support customers, we are always happy to welcome new beta testers - particularly those using Eclipse/CDT. If you would like to become a beta tester please contact us.