PC-lint用户手册：C++软件诊断与使用指南

4星 · 超过85%的资源需积分: 10 22 浏览量更新于2024-07-25 收藏 4.48MB PDF 举报

PC-lint/FlexeLint 用户手册是一份详尽的指南，专为C和C++软件开发人员设计，旨在帮助他们有效利用这款诊断工具。该手册适用于PC-lint软件的9.00版本及后续更新，发布日期为2008年9月。Gimpel Software，一家位于美国宾夕法尼亚州Collegeville的公司，是该产品的开发者，提供了联系方式（电话和传真）以及官方网站地址。手册的核心内容包括了对PC-lint功能的详细介绍，它作为一款代码质量检查工具，旨在发现并修复潜在的编程错误、风格问题和一致性问题。通过使用此工具，开发人员可以提高代码的可读性、健壮性和效率。PC-lint支持C和C++语言，并在设计时考虑到了严格的规则和最佳实践。在手册中，用户可以找到关于如何设置和配置PC-lint的章节，包括如何添加自定义规则、配置警告级别和处理不同类型的错误。此外，还有关于使用内置分析器进行静态代码分析的指导，这有助于识别代码中的缺陷，比如未使用的变量、未初始化的内存、不安全的类型转换等。值得注意的是，版权方面，Gimpel Software明确声明所有权利保留，未经书面许可，禁止任何形式的复制、传播、转录或翻译其作品。同时，手册也包含免责声明，Gimpel Software虽然已经尽力确保内容的准确性和有效性，但并不担保手册内容或附带的电子媒体程序和数据的适用性，也不对特定用途的适配性做出保证。用户在使用PC-lint时应自行负责，可能存在的更新和变更可能不会提前通知。 PC-lint用户手册是一份不可或缺的参考资源，对于希望提升代码质量和遵循最佳开发实践的开发者来说，它是优化代码质量控制流程的重要工具。阅读和理解这份手册将有助于开发人员更有效地利用PC-lint进行代码审查和维护工作。

For FlexeLint you will arrive here after creating an equivalent Shell script (or equivalent

command script), which for presentation purposes we assume is named

lin. In this section, to

describe the basic operation of the product we assume two small files

filea.cpp and

fileb.cpp defined below. These may be found in directory dos-ins\test of the PC-lint

distribution disc or you might find it less trouble to type them in fresh.

From your configuration directory type

lin filea fileb

This applies PC-lint to the sample files filea.cpp and fileb.cpp shown below.

// filea.cpp:

//lint -w2 reduce the warning level to 2

class X

{

static int a;

};

// fileb.cpp:

class X

{

int a;

};

You should see on your screen approximately the following message:

PC-lint for C/C++ (NT) Vers. 9.00, Copyright ...

--- Module: filea.cpp (C++)

--- Module: fileb.cpp (C++)

};

fileb.cpp 5 Warning 631: tag ’X’ defined differently at line 4, file

filea.cpp

filea.cpp 4 Info 830: Location cited in prior message

--- Global Wrap-up

Warning 1527: static member ’X::a’ (line 6, file filea.cpp) not defined

filea.cpp 6 Info 830: Location cited in prior message

Not everything you see is an error message. The opening line identifies the version of PC-lint

(and the version of the DOS extender if you are running the DOS executable). The 2nd and 3rd

lines are in-progress messages, which normally just display the names of the modules being

processed. They are essentially a way of giving a progress report when PC-lint/FlexeLint is

processing many files and nothing else is being reported. You can turn off these 'verbosity'

messages or increase their detail with the

-v... option.

The 4th line is the start of an error message. Normally, an error message will begin with a pair of

lines. The first line contains only the character ‘

_‘ which points (downward) to the place on the

second line (the actual line of source code) where the error was first encountered. This is

followed by a line containing, in order, the name of the file being processed, the line number, the

kind of message (Error, Warning, Informational, Elective Note) a message number and a brief

description. It is important to note that a more complete description can be found by looking up

the message number toward the end of this manual (Chapter 19. MESSAGES).

In many cases (including this example) a prior point in the program is referenced. The name of

the file and, possibly, the name of the module are given. (If the error had occurred in a

#include

file, the filename would have been different from its module name and hence both would have

been given).

You will note in particular Message 830 which is issued for the sole purpose of allowing an

automatic error processor to go to the location cited within the immediately preceding message.

Any option can be placed within a file within a special C or C++ comment as is shown in

filea.cpp. The only thing special is that the comment begins immediately with the word lint.

As an experiment, remove the special nature of the comment by introducing a blank before the

word

lint. You have changed the warning level to 3 (the default) and a richer set of diagnostic

messages will issue forth.

There are ways of customizing the format of error messages, especially for the automatic

processing of messages. See Section 5.6 Message Presentation Options

It is not normally necessary to perform further tests, but running the remaining tests can be

instructive.

Create a convenient directory for the purpose and copy in all the files from

InstDir\test.(If

you have used

INSTALL to get here (See Section 3.7 Other Operating Systems), rather than

SETUP, you should copy the files from the distribution disc in directory \dos-ins\test.)

For every file of the form

test?.lnt

there will be a corresponding output file named:

test?.out

To run the first of these type at command level:

beta.c

gamma.c

then use:

lin alphabet

to lint the entire project. You may place options within alphabet.lnt but this is not

recommended because if you then do a unit checkout on individual modules, you will not receive

the benefits of these options. Better, place project-independent options in a centralized file; we

have started you off with the file

options.lnt for this purpose. Project-specific options can be

placed in a file called

std.lnt in your project directory. This std.lnt should be an

augmentation of the centralized

std.lnt. This is further described in Section 16.2

Recommended Setup.

3.5 Integrating With Your Environment

PC-lint has been flexibly designed so that you should have no difficulty integrating it with your

favorite Integrated Development Environment (IDE), or smart editor. The advantages are that

you will be able to launch PC-lint with a minimum number of keystrokes to process your current

file or your current project. Upon completion, moreover, you will be able, in most cases, to

quickly and automatically sequence from error to error (actually message to message) with

hopefully a single keystroke and with your own editor appropriately positioned in the file that

needs attention.

We, of course, could have provided our own environment but we felt you probably would prefer

to continue using your existing environment with your favorite editor. Hence, we have focused

our attention on facilities to bring that about. In particular, our message formatting is extremely

flexible (See Section 5.6 Message Presentation Options). Message redirection is available not

only via the standard redirection character (>) on the command line but may also be embedded as

an option (see

-os(file) in Section 5.7 Other Options). The banner line can be controlled (see

-b in Section 5.7 Other Options) and it can be arranged so that at least one message is always

produced (using option

+e900) which is necessary for some environments. In addition, indirect

files (

.lnt files) can themselves contain indirect files. The file name extension, by which an

indirect file is known as such, can be something other than .lnt (See +ext in Section 5.7 Other

Options). Indirect files can contain embedded environment variable names (Section 4.1 Indirect

(.lnt) Files).

We have added a number of files of the form

env-....lnt that assist in the process of integration

with particular IDE's. These files are updated as needed. See our web site (under Version 9.00

patches) for the most current.

Instructions for using these

.lnt files appear as comments within the files themselves. Simply

print them out and follow the directions.

剩余531页未读，继续阅读

suminet

粉丝: 0
资源: 1

PC-lint用户手册：C++软件诊断与使用指南

PC-LINT9.0在keil5中的使用教程

pclp-1_plus_PClintplus_pclintplus下载_pc-lintplus_pc-lint

pc-lint用于sourceinsight上静态代码检测

pc-lint v1.3.part3_Lint_pc-lintv1.3_pc-lint_PClint_

PC-lint8-w.rar_insight_pc lint 8_pc-lint_pclint9

PC-Lint-GUI:基于Qt的PC-Lint GUI

PC-lint 9.0 -- Gimpel.Software.PC-lint.9.0a

pc-lint和pc-lint plus有什么区别，详细说明。为什么一个有linux版本一个没有。

pc-lint v1.3.part1_pc-lintplus_PC-lintplus1.35_Lint_PC-lintPlus1

PCLint.rar_Lint_pc-lint_pclint

最新资源