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

lint

manual

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

身份认证购VIP最低享 7 折!

30元优惠券

资源详情

资源推荐

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++软件诊断与使用指南

pclp-1_plus_PClintplus_pclintplus下载_pc-lintplus_pc-lint

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

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

PC-lint配置与使用指南

PC-lint安装与配置指南

SourceInsight与PC-Lint集成指南

Source Insight与PC-Lint集成教程

Visual Studio与PC-lint Plus结合使用指南

pc-lint plus如何在linux上使用，详细步骤

pc-lint plus 使用教程

pc-lint的安装方法，不安装在C盘中可以吗？

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

windows安装PC-lint

pc-lint source insight

docker --lint

pc-lint如何在linux上使用

git-commit-lint-vscode

eden-lint --fix

'browserslist-lint' 不是内部或外部命令，也不是可运行的程序 或批处理文件。

如何安装babel, vue-router, vue-x, less, es-lint, element-ui, axios

最新资源

'browserslist-lint' 不是内部或外部命令，也不是可运行的程序或批处理文件。