The OPTIONS @ statement overrides compiler command-line options.
OPTIONS /qualifier [/qualifier ]
The following table shows the OPTIONS statement qualifiers:
Table 4-4 OPTIONS Statement Qualifiers
Qualifier |
Action Taken |
---|---|
/[NO]G_FLOATING |
None (not implemented) |
/[NO]I4 |
Enables/Disables the -i2 option |
/[NO]F77 |
None (not implemented) |
/CHECK=ALL |
Enables the -C option |
/CHECK=[NO]OVERFLOW |
None (not implemented) |
/CHECK=[NO]BOUNDS |
Disables/Enables the -C option |
/CHECK=[NO]UNDERFLOW |
None (not implemented) |
/CHECK=NONE |
Disables the -C option |
/NOCHECK |
Disables the -C option |
/[NO]EXTEND_SOURCE |
Disables/enables the -e option |
The OPTIONS statement must be the first statement in a program unit; it must be before the BLOCK DATA, FUNCTION, PROGRAM, and SUBROUTINE statements.
Options set by the OPTIONS statement override those of the command line.
Options set by the OPTIONS statement endure for that program unit only.
A qualifier can be abbreviated to four or more characters.
Uppercase or lowercase is not significant.
For the following source, integer variables declared with no explicit size occupy 4 bytes rather than 2, with or without the -i2 option on the command line. This rule does not change the size of integer constants, only variables.
OPTIONS /I4 PROGRAM FFT ... END
By way of contrast, if you use /NOI4, then all integer variables declared with no explicit size occupy 2 bytes rather than 4, with or without the -i2 option on the command line. However, integer constants occupy 2 bytes with -i2, and 4 bytes otherwise.