🚀 go-pugleaf

On 11 Jun 1996 05:32:55 GMT, smeyers@teleport.com (Scott Meyers)
wrote:

>Martin Klaus and I are undertaking an examination of lint-like tools
>designed for C++ programs, i.e., tools that look for suspect usage of
>C++ features in source code and issue appropriate warnings.  Examples
>of such likely errors might include declaration of public data
>members or failure to declare a virtual destructor in a base class.  
>
>We have identified the following vendors and tools as candidates for
>our study: 
>
>    Abraxas Software:              CodeCheck      
>    Centerline Software:           C++Expert      
>    Gimpel Software                Flexelint/PC-Lint 
>    HP:                            CodeAdvisor    
>    ParaSoft:                      CodeWizard
>    Programming Research:          QA/C++         
>    Productivity Through Software: ProLint        
>
>If you have personal experience with any of these tools, or if you
>know of additional tools that check C++ usage that are not listed
>here, I'd greatly appreciate it if you'd send me mail about it.
>
>Note that we are only interested in tools that provide nontrivial
>support for C++ source code.  We do not wish to consider tools that deal
>only with the C subset of C++, nor are we much interested in tools that
>focus on a program's dynamic behavior (e.g., monitors of memory usage). 
>
>Thanks for your help,
>
>Scott
>smeyers@netcom.com

Hi

I think you left out:

Borland    CodeGuard
NuMega   BoundsChecker

Or else I didn't read you
Anyway Gimpel has now a C++ Lint

Ziv