| Feature |
Standard Edition
from $199 USD
|
Professional Edition
from $399 USD
|
Enterprise Edition
from $799 USD
|
| C/C++ analysis using PC-lint, CppCheck, cpplint.py or Vera++ |
 (one analysis tool) |
 (one analysis tool) |
 (all available tools) |
| C# analysis using FxCop or (coming soon) TICS Basic for C# (formerly ClockSharp) |
 (one analysis tool) |
 (one analysis tool) |
 (all available tools) |
| Java analysis using FindBugs |
Under development |
Under development |
Under development |
| Plug-ins for Visual Studio (VS2002/2003/2005/2008/2010, VC6 and eVC4) and Eclipse |
 (one plug-in) |
 (one plug-in) |
 (all available plug-ins) |
| Compatible with the Intel C++ Compiler (version 9.1 or later, in VS2005/2008) |
- |
 |
 |
| Designed for large codebases |
- |
 |
 |
| Dedicated command to view the manual/helpfile for the active analysis tool within the development environment |
 |
 |
 |
| Dedicated commands to edit the configuration of the active analysis tool directly within the development environment |
 |
 |
 |
| Analysis of implementation files automatically takes into account project settings and active configuration |
 |
 |
 |
| The active file can be manually analysed from the context menu of the code editor at any time |
 |
 |
 |
| Double clicking on an analysis issue opens the corresponding source file and shows the meaning of the issue |
 |
 |
 |
| Single file ("unit checkout") manual analysis |
 |
 |
 |
| Automated background analysis of the entire solution or workspace |
 |
 |
 |
| Selective inclusion or exclusion of individual projects and files from background analysis |
- |
 |
 |
| PC-lint whole project (i.e. intermodule) analysis |
- |
 |
 |
| Analysis results automatically are made available when a file is opened for editing |
 |
 |
 |
| Code Editor markers indicate the location and severity of analysis issues (VS2005/2008/2010) |
- |
- |
 |
| When a file is saved, it is automatically queued for re-analysis |
 |
 |
 |
| A dedicated Analysis Results Display presents analysis results in an easy to interpret, colour coded form |
 |
 |
 |
| Global Display Filter allows issues with a specific ID to be instantly filtered from the displays |
- |
- |
 |
| Insert suppression directives (e.g. //lint !e1762) directly from the Analysis Results Display |
- |
- |
 |
| Analysis Results Display "Issue Count by Category" view |
- |
 |
 |
| Analysis Results Display "Issue Count by Message Number" view |
- |
- |
 |
| A dedicated Message Lookup Display provides the ability to directly look up the meaning of any PC-lint message |
 |
 |
 |
| A dedicated Analysis Status Display shows detailed information upon the current status of analysis within the solution |
 |
 |
 |
| A dedicated Analysis History Display showing information upon the analysis history of a specified file, project or the entire solution |
- |
- |
 |
| HTML Reports |
 |
 |
 |
| User defined HTML report stylesheets |
- |
 |
 |
| Analysis reports include detailed breakdowns (in chart and tabular form) of which issues have been reported, and where |
- |
- |
 |
| Customised per solution and per project analysis configurations |
- |
 (stored with solution only) |
 (stored with solution or project) |
| Post-processing of generated PC-lint project.lnt files |
- |
- |
 |
| Customisable and user definable issue categories (currently PC-lint only) |
- |
 |
 |
| Accelerate local PC-lint analysis tasks using PC-lint 9.0 precompiled headers |
- |
 |
 |
| Accelerate analysis tasks using spare processing capacity on your network (requires Xoreax IncrediBuild) |
- |
- |
 |
| |
Detailed Pricing |
Detailed Pricing |
Detailed Pricing |