fpt Reference: CHECK - Combined QA Checks

fpt and WinFPT Reference Manual - Command-line Commands

| SimCon Home | Ref Manual Home |

CHECK

Syntax:

[NO] CHECK

Function:

The command CHECK written without arguments is equivalent to the combination of the commands:

CHECK ALIGNMENT - Checks that objects start on aligned addresses in memory;
CHECK ARGUMENTS - Checks that the arguments passed to sub-programs are of the correct data type, data size and array bounds, and are accessed legally;
CHECK DATA TYPE COERCION - Checks for dangerous data type coercions, e.g. IF (ie) THEN where ie is an integer variable;
CHECK EQUIVALENCE - Checks for objects of different types which occupy the same memory addresses and for objects which share the same addresses without an explicit EQUIVALENCE declaration;
CHECK NAMES - Checks that the same name is used consistently in different sub-programs, in particular that objects with the same name do not occupy different COMMON block addresses;
CHECK USAGE - Checks for objects which are read but never written, written but never read, or declared but never used.

The CHECK command is conveniently used to carry out a QA analysis of a suite of software. Please note that it is the responsibility of the user to set up default values for the filters which control the sensitivity of these checks, using commands such as NAME CHECK TO IGNORE LOCALS and ARGUMENT CHECK TO IGNORE ARRAY BOUNDS. These are most conveniently set up in the configuration file, config.fsp, or in the fsp file which lists the files to be processed.

The command NO CHECK suppresses all of these checks. It is most often used to prevent the check requested in fsp files from starting when fpt is run interactively. The checks may be run interactively one at a time.

Where to Use this Command

Operating system command line	Yes
Configuration file, config.fsp	Yes
Specification (fsp) files, *.fsp	Yes
Interactively, to FPT> prompt	Yes
Interactive command files	Yes
Embedded in the Fortran code	Yes

Default

The checks are not carried out by default (Note that defaults may be changed in the configuration file).

Examples:

Carrying out a QA analysis (Windows)

D:\Dave\Test> fpt heli.fsp /check

Suppressing checks requested in the FSP file when running interactively (Unix)

$ fpt heli.fsp "%no check" %i