pTAL Reference Manual (G06.24+, H06.09+, J06.03+)

OPTIMIZE

level

EffectLevel

Code is not optimized. Provided in case other optimization levels cause errors or interfere with

debugging. Supports symbolic debugging; data is always in memory.

Code is optimized within statements and across statement boundaries. The resulting code is

more efficient than that produced by lower levels of optimization and does not interfere with

debugging.

Code is optimized within statements and across statement boundaries, and the resulting code

is more efficient than code produced by lower levels.

NOTE: If your program compiles successfully at level 0 but runs out of memory at level 1 or

2, either compile your program only at level 0 or split your program into smaller subprograms

and compile those at the same higher level.

OPTIMIZE 1Default:

Outside the boundary of a separately compiled programPlacement:

The optimization level active at the beginning of a separately compiled program

determines the level of optimization for that program and any programs it

contains

Scope:

None, but OPTIMIZEFILE can override OPTIMIZE in individual proceduresDependencies:

OPTIMIZEFILE (page 404)References:

OPTIMIZEFILE

OPTIMIZEFILE sets the optimization level for individual procedures and subprocedures.

filename

is an EDIT file on Guardian platforms and a text file on Windows platforms. Each line of the

file must have this syntax:

(See Example 350 (page 405).)

404 Compiler Directives