PC-lint/FlexeLint 8.0参考手册：最全面的诊断工具

3星 · 超过75%的资源 | 下载需积分: 50 | PDF格式 | 3.67MB | 更新于2025-01-06 | 22 浏览量 | 举报

1 收藏

"Flexelint Reference - 最全的版本，适用于C和C++软件的诊断工具，版本8.00及以后，由Gimpel Software提供。" Flexelint是一款强大的静态代码分析工具，用于检查C和C++程序中的潜在错误、编程规范问题以及可能的安全漏洞。它在软件开发过程中起着至关重要的作用，帮助开发者在编译阶段就能发现并修复问题，提高代码质量和可维护性。这份"Flexelint Reference Manual"是针对Flexelint 8.00及其更高版本的详细指南。手册包含了丰富的信息，涵盖了各种警告和错误消息的解释，以及如何配置和使用Flexelint进行有效检查。内容可能包括： 1. **基本概念**：介绍Flexelint的基本工作原理，如何理解和解读其生成的诊断信息。 2. **使用指南**：详述如何安装、配置和运行Flexelint，包括命令行参数、配置文件设置等。 3. **检查类别**：列举了Flexelint能够检查的各种编程问题，如类型匹配、内存管理、未初始化的变量、潜在的空指针异常、循环优化等。 4. **规则定制**：说明如何根据项目需求自定义检查规则，控制哪些警告应被视为错误，哪些可以忽略。 5. **集成开发环境（IDE）支持**：如果适用，会介绍如何将Flexelint集成到常见的IDE如Visual Studio或Eclipse中，实现无缝的编码和分析体验。 6. **报告和输出**：解释如何格式化和解析Flexelint的输出结果，以及如何生成详细的报告。 7. **错误处理和解决策略**：提供了关于如何分析和修复由Flexelint识别的问题的指导。 8. **版本更新**：可能会提及从早期版本升级到8.00的注意事项，以及新版本带来的改进和新增功能。 9. **法律条款**：文档最后通常包含版权信息和免责声明，强调Gimpel Software不提供任何明示或暗示的保修，并保留对产品规格和手册内容进行更改的权利。通过使用Flexelint Reference，开发者不仅可以提升代码质量，还可以遵循最佳实践，确保代码符合行业标准和组织内部的编码规范。对于任何希望提升C和C++代码质量的团队来说，这是一份不可或缺的参考资料。

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页未读，继续阅读

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

30元优惠券

phil阿良

粉丝: 0

PC-lint/FlexeLint 8.0参考手册：最全面的诊断工具

PDF+Reference+1.6+中文版

PDF Reference 1.7 中文版+1.6中文版+PDFPatcher检测

PDF reference 1.6中文版

brew reference brew reference brew reference

OpenGL Reference Manual OpenGL Reference Manual

MySQL 5.6 Reference Manual MySQL 5.6 Reference Manual

A Java Reference: Assorted Java Reference Material

DFSSORT reference

gtk reference

reference引用

最新资源