As a general observation when integrating PC Lint ALL paths should be FULLY specified. Directory and file names should not contain any spaces. The following IDE's are catered for or under development:-

 You might wonder why you would want to integrate Lint into a version control system. The answer is quiet simple and obvious. So obvious you might wonder, as I did why this is not already set up in the version control tools at the outset!

The idea behind Version or Revision control (RCS, SCVS, SCCS, VCS etc) is that you can track every version of the source and always retrieve any version of the source.. The main database is therefore very important (and should be backed up regularly). You want only code that does not have any errors in the database.

So you mandate in your Coding Standard or Development Procedures that ALL C or C++ source code passes clean through lint before it is checked in to the VCS. That's the problem solved!

Well maybe. You can trust your engineers to always run lint (at the required settings) and only check in if it is a clean pass?... really? The answer is to use the system that virtually all VCS systems have. A triggers and scripts.

The triggers permit things like if a file of "filename" or type "*.C" is checked in run this script. This can do a multitude of things including running lint have several out comes:- check the file in, don't check in, load file back into an editor with the errors.

Below I have presented several scripts for this.

Coming soon scripts for MKS, PVCS, Source Safe, Clear Case, Perforce CS-RCS

 Copyright Chris A Hills 2002
The right of Chris A Hills to be identified as the author of this work has been asserted by him in accordance with the Copyright, Designs and Patents Act 1988