Products, the Universe and Everything

The Riverblade Developer's Blog

Beth demonstrating Visual Lint at the ACCU Conference 2008  Anna taking part in a discussion panel at the European Software Conference 2007 

Welcome to our developer's blog. We hope that this forum provides an insight into us, our products and how we develop them. Please feel free to write to us if you have anything to add to any of the posts here.

Current Entries | Archives |


LintProject Professional has been released
Saturday, January 24, 2009

Since it was first publicly released in 2004, our command line code analysis tool LintProject has gathered a significant amount of interest from Visual C++ developers.

However, although the code has been significantly revised since then LintProject is now showing its age. In particular, the HTML reports it generates are very basic (being limited to issue counts and raw analysis results), and - as it relies on PC-Lint to generate project.lnt files (unlike Visual Lint, which does this directly) - it can have difficulty with project files containing either Visual Studio environment variables or inherited property sheet (.vsprops) files.

While we were developing the (much more detailed) reports for Visual Lint 2.0, it occurred to us that it would be worth conducting a feasibility study to determine whether the Visual Lint reporting and project file handling code could be back ported to LintProject.

As it turned out, it could - and as a result we have now been able to develop LintProject Professional which not only produces the same type of detailed analysis reports as Visual Lint Enterprise Edition, but also supports project configurations (such as those using .vsprops files) which are far beyond the capabilities of LintProject.

You can view an example report of the type generated by LintProject Professional at http://www.riverblade.co.uk/products/lintproject/example.

We've been using LintProject Professional on our build server for several months already, and it has already proved to be far more useful than its predecessor. We hope you find it as useful as we do.

Posted by Anna at 17:19 | Get Link

 

PC-Lint 101: What does "Location cited in prior message" mean?
Tuesday, January 20, 2009

If you are new to PC-Lint, you may have wondered what message 830 ("Location cited in prior message") means, and - given that such messages can add greatly to the overall issue count in your file or project - what (if any) use are they?

Quite simply, message 830 identifies a location in the codebase which relates to the preceding message (or issue, in Visual Lint terminology).

For example, if you analyse the code shown below (lines with lint issues are highlighted in yellow):


the analysis results you will see are likely to look something like this (note the four occurances of message 830, each following another message):


If you examine the contents of the lines referenced in the 830 messages, you will find that they are where the functions referred to in the "Ignoring return value of function" messages are defined:


The beauty of this within the development environment is of course that by double clicking on the "Location cited in prior message" issue, you will be taken directly to the definition of the function concerned, so you can easily view its definition and (in this context) see what it returns.

Incidentally, there is a similar message - 831 ("Reference cited in prior message") - which identifies other supporting information for a message. It works in exactly the same way as 830.

Posted by Anna at 11:05 | Get Link