Gimpel Software Links

	Order Lint 9.00 Patches Discussion Forum
Contact Site Map

Cleanscape C++Lint
provides ease-of-use enhancements including three user interfaces:
(a) a graphical user interface with point and click control of PC-lint's analysis with hyperlinks to numerous code editors
(b) deep integration with Visual Studio, automated by Cleanscape
(c) the classic command line with return codes for scripts or builds

Visual Lint from Riverblade
is an add-on software product which allows you to more effectively run PC-lint from within Microsoft Visual Studio and even provides for automatic background linting of your code.

LintProject from Riverblade
is a command line tool to enhance your use of PC-lint with Visual C++. LintProject can be run against a Visual C++ project or solution file (.dsp, .vcproj, .sln or .dsw), and will tell PC-lint which source files to analyse. It will write XML and HTML reports which link to your PC-lint output and indicate how many warnings were found within each implementation file, project and solution. These reports are automatically refreshed in real time so you can follow the progress of PC-lint's analysis of your code.

PC-lint Windows Help File from Dreamcycle Now supporting Version 9.0
Have you ever wished you had a help file of PC-lint messages that you could access from within your IDE? Check out Scott's web page - it may be just what you're looking for.

PC-lint Tutorial from Johan Bezem
"How To Wield PC-lint" is an excellent tutorial for new users, but also contains useful information for the PC-lint pro.

HLL - Heuristic Lint issue Locator by Ralf Holly. After a PC-lint run, you frequently want to know what exactly a warning is about. In this case, you fire-up ‘msg.txt‘ and search for the error number. With HLL (a Perl script) it's much easier: just pass it the error number (or numbers) and it extracts the corresponding parts from ‘msg.txt’ and displays them on the console.

Lint Metrics & ALOA by Ralf Holly, C/C++ Users Journal, June 2004
"ALOA (short for A Lint Output Analyzer) is a tool that processes output generated by PC-lint and computes various useful metrics that give a quick overview of the internal quality of any C/C++ project. Furthermore, it shows which kind of Lint issues are most frequently encountered and highlights issue-laden modules. The metrics produced by ALOA are useful for tracking a project's lint compliance and for fine-tuning Lint policies."

"A Report Generator for PC-lint" by Jon Zyzyck, Dr. Dobb's Journal February 2003

"Automated Defect Identification" by Kevin Smith, Dr. Dobb's Journal February 2003

All About Lint -- PC-lint and Windows Drivers, The NT Insider , September-October 2002

JB Enterprises ( j.bezem@computer.org ) www.bezem.de
"How To Wield PC-lint" Johan Bezem's excellent tutorial and tips

Rich Miller is an expert in using PC-lint to rapidly increase product quality and to sustain these gains by incorporating PC-lint into effective software build processes. He has applied PC-lint to a number of products at various companies, including GE Healthcare and Raima Corporation, starting in 1991. He’s found that the success factors include the simplicity of how the software is used and the change management processes around it. By focusing on key errors (often up to several thousand serious-to-critical bugs per product), organizations can improve quality aggressively, and then further increase the quality over time. Rich is available on a consulting basis for mentoring, training, and - most importantly - hands-on, collaborative fixing of software defects with existing teams. Email: Rich.Miller.6@gmail.com

If you have information that you think should be added to this page, please email it to "anneliese" at gimpel.com