PC-Lint使用手册：C/C++软件诊断工具

3星 · 超过75%的资源需积分: 16 42 浏览量更新于2024-07-28 收藏 3.67MB PDF 举报

"PC-Lint使用手册.pdf 是一份关于PC-Lint/FlexeLint的参考手册，主要针对C和C++软件，适用于版本8.00及其后续版本。该手册由Gimpel Software出版，详细介绍了这个强大的诊断工具，旨在帮助开发者提升代码质量和效率。手册内容涵盖PC-Lint的功能、用法和可能的警告或错误信息。" PC-Lint是一款著名的静态代码分析工具，它主要用于检查C和C++程序中的潜在错误、不符合编程规范的地方以及可能的性能问题。它可以在编码阶段就发现并报告问题，而不是等到编译或运行时，从而提高软件的可靠性和维护性。手册的详细内容可能包括以下几个方面： 1. **基础概念**：解释PC-Lint的基本原理，如何通过扫描源代码来识别潜在问题，以及如何配置和定制检查规则。 2. **警告和错误信息**：列出各种可能的警告和错误代码，每个代码都有详细的解释，包括它代表的问题类型、如何触发以及如何修复。 3. **使用指南**：指导用户如何集成PC-Lint到他们的开发环境中，如IDE、构建系统或者命令行工具的使用。 4. **配置选项**：介绍如何通过设置文件控制PC-Lint的行为，例如忽略特定警告、启用额外检查或针对特定项目调整敏感度。 5. **报告分析**：讲解如何解读PC-Lint生成的分析报告，理解问题的严重性以及优先级，以优化修复工作流程。 6. **最佳实践**：提供有关编写更高质量代码的建议，包括遵循编程标准、避免常见陷阱和优化代码结构。 7. **案例研究**：可能包含实际项目中的例子，展示如何利用PC-Lint解决特定问题或改进代码质量。 8. **技术支持与更新**：提供获取Gimpel Software技术支持的途径，以及如何获取最新的工具更新和补丁。 9. **法律声明**：强调版权信息，指出未经许可不得复制、传播或翻译手册内容，同时也提醒用户，尽管Gimpel Software努力确保手册和程序的有效性，但不提供任何明示或暗示的保修。通过这份手册，开发者可以深入理解PC-Lint的功能，并有效地利用它来提高代码质量和软件工程的效率。同时，手册中的免责声明表明，尽管PC-Lint是强大的工具，但用户仍需自己负责对结果进行判断和处理。

mational, 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 17. MESSAGES).

In many cases (including this example) a prior point in another module 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).

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. You will note in

particular Message

832

which is issued for the sole purpose of allowing an automatic error processor to

go to the location cited within the immediately preceding message as described in the previous paragraph.

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 an output file on the distribution disc named:

test?.out

To run the first of these type at command level:

lint test1.lnt

and you should observe on the screen information identical to test1.out.

Other test suites are run similarly.

3.4 Linting your Programs

To lint your own programs, enter a directory containing your C and C++ modules. We assume a lin.bat

(or equivalent shell script in the host operating system) that can be run from any directory (i.e., has been

placed in your

PATH). This has the advantage of simplifying the presentation and perhaps simplifying the

typing.

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 con-

tinue 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 Sec-

tion 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 par-

ticular IDE's. At this writing this list includes:

File Environment

env-BC5.lnt Borland's 5.0 IDE

env-bwin.lnt Borland's 4.0 IDE under Windows

env-cw.lnt Premia Codewright

env-pwb.lnt Microsoft's Programmer's Work Bench

env-si.lnt Source Insight Editor

env-sled.lnt Visual Slick Edit

env-tide.lnt Turbo/Borland IDE under DOS

env-vc.lnt Microsoft's Visual C/C++, Version 1

env-vc2.lnt Microsoft's Visual C/C++, Version 2

env-vc4.lnt Microsoft's Visual C/C++, Version 4

env-vc5.lnt Microsoft's Visual C/C++, Version 5

These files are updated as needed. See our web site (under Version 8.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.

3.6 .dsp processing

If you are using Microsoft Visual Studio, then an abstract of each project is retained in a file whose exten-

sion is

.dsp. This file is in ASCII and can be viewed with your editor. The file contains module names,

defines of pre-processor variables, and include paths. PC-lint/FlexeLint is able to process such files,

extract such information as would be related to linting, transform the information to lint directives and out-

put the result to standard output. The resulting file, if it has a .lnt extension, can be used as input to

PC-lint/FlexeLint. For example, the following creates a lint project file from a

.dsp

file.

lint-nt project.dsp >project.lnt

The .dsp file is, among other things, inspected for SOURCE= lines. These lines contain not only names of

modules (C and C++ files), but headers, resource files, text files, etc. PC-lint/FlexeLint, of course, wants

just the module names. By default, we select out any file whose extension is "

.c" and any file that bears a

C++ extension. By default, C++ extensions are "

.cpp" and ".cxx" but this list of extensions can be con-

trolled via the -

cpp option. Note that if a programmer had an unusual C extension it could be dubbed a

C++ extension just for the purpose of file extraction. This gives the user complete control over which files

are selected as modules.

To gain some insight into how the translation is being done, you may use the verbosity option to trigger a

message for each line. Thus:

lint-nt -v1 project.dsp >project.lnt

will provide a line-by-line account of the translation.

Within a

.dsp file, there are conditional statements such as

!IF "$(CFG)" == "project - Win32 Release"

which allows you to select debug or release variants. Variable CFG is generally specified to the most recent

configuration within the

.dsp file. You can change the flow via a "command line" option:

+d"CFG=project - Win32 Release"

This is like a pre-processor define except that the +d (as opposed to -d) prohibits subsequent redefinition.

The use of quotes is necessary because the define contains blanks. Since there are a variety of ways of

parsing command line parameters (batch command, make file, command line) and since the ways of deal-

ing with quotes and blanks are all slightly different, it is best to place this option in a separate

.lnt file

such as:

release.lnt:

+d"CFG=project - Win32 Release"

and then use a command line such as:

lint-nt release.lnt project.dsp > project.lnt

As indicated above, the output file (project.lnt in these examples) will contain useful options as well as

a list of modules. For unit checkout, you may want the list of options but not the list of modules. For this

purpose, use the --

u option (as opposed to -u). For example:

lin --u project.lnt alpha.cpp

剩余366页未读，继续阅读

ho012tpiu

粉丝: 7

PC-Lint使用手册：C/C++软件诊断工具

pc-lint使用经验

pc-lint 经验（中文）

PC-lint 9 中文手册.pdf

PC-Lint教材

PC-Lint参考资料

PC-Lint-9.0E 附带教程

PC-lint 9中文手册：深入代码检查工具的使用与技巧

PC-lint配置与使用指南

PC-Lint安装与使用指南

PC-lint安装与配置指南

最新资源