* ALL_STATIC_ON, ALL_STATIC_OFF
These directives control where procedure local variables are
allocated. ALL_STATIC_ON turns allocation of procedure local
variables in the data space ON, regardless of the keyword STATIC
being used or not. ALL_STATIC_OFF places procedure local
variables in the stack space. The default is ALL_STATIC_OFF.
* RANGE_ON, RANGE_OFF
Turns generation of rangecheck code ON and OFF.
* USE_SEIZE_FILE <character string literal>
Specify the filename (as a character string literal) where
subsequent SEIZE statements are related to. This directive and the
subsequent SEIZEs are written to a possibly generated grant file
for this module.
<> USE_SEIZE_FILE "foo.grt" <>
* USE_SEIZE_FILE_RESTRICTED "filename"
Same as USE_SEIZE_FILE. The difference is that this directive and
subsequent SEIZEs are *not* written to a possibly generated grant
* PROCESS_TYPE = <integer expression>
Set start value for all PROCESS delclarations. This value
automatically gets incremented after each PROCESS declaration and
may be changed with a new PROCESS_TYPE compiler directive.
* SIGNAL_CODE = <integer expression>
Set start value for all SIGNAL definitions. This value
automatically gets incremented after each SIGNAL definition and
may be changed with a new SIGNAL_CODE compiler directive.
* SEND_SIGNAL_DEFAULT_PRIORITY = <integer expression>
Set default priority for send signal action.
* SEND_BUFFER_DEFAULT_PRIORITY = <integer expression>
Set default priority for send buffer action.
Note: Every <integer expression> in the above mentioned compiler
directives may also be specified by a SYNONYM of an integer type.
SYN first_signal_code = 10;
<> SIGNAL_CODE = first_signal_code <>
automatically generated byinfo2html