FIX: F4998 Not Generated for Variable in CALL Statement (84594)
The information in this article applies to:
- Microsoft FORTRAN Compiler for MS-DOS 5.0
- Microsoft FORTRAN Compiler for MS-DOS 5.1
- Microsoft FORTRAN compiler for OS/2 5.0
- Microsoft FORTRAN compiler for OS/2 5.1
- Microsoft FORTRAN PowerStation for MS-DOS 1.0
- Microsoft FORTRAN PowerStation for MS-DOS 1.0a
- Microsoft Fortran Powerstation 32 for Windows NT 1.0
This article was previously published under Q84594 SYMPTOMS
When a variable is a part of an expression that is an actual argument in a
CALL statement but is not otherwise defined, Microsoft FORTRAN does not
generate the F4998 "variable used but not defined" warning message even
though the compiler is designed to do so.
CAUSE
Normally, the compiler does not check actual arguments to verify that a
value has been assigned to an argument. When a CALL statement uses an
expression as its actual argument, the compiler should check all components
of the expression to verify that the application assigned a value to each
of them.
RESOLUTION
To ensure that this warning message occurs for each variable in an
expression used in a CALL statement, modify the source code to assign each
expression to a temporary variable and specify the temporary variable as
the argument in the CALL statement.
STATUS
Microsoft has confirmed this to be a bug in the products listed above. This
problem was corrected in FORTRAN PowerStation version 4.0.
Modification Type: | Major | Last Reviewed: | 12/1/2003 |
---|
Keywords: | kbCompiler kberrmsg kbfix KB84594 |
---|
|