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

NODEFAULT

specifies that every structure declaration must include a FIELDALIGN (page 395).

FIELDALIGN AUTODefault:

Placement:

• Can appear only once in a compilation unit

• Must precede all declarations of data, blocks, and procedures

Applies to the compilation unitScope:

NoneDependencies:

FMAP

lists the file map in the compiler listing.

NOFMAP

suppresses the file map in the compiler listing.

NOFMAPDefault:

Anywhere, any number of times. The last FMAP or NOFMAP in the compilation

unit determines whether the compiler lists the file map.

Placement:

Applies to the compilation unitScope:

FMAP has no effect if either NOLIST or SUPPRESS is activeDependencies:

References:

• LIST (page 401)

• SUPPRESS (page 420)

The file map:

• Appears after the map of global identifiers in the compilation listing

• Starts with the first file that the compiler encounters and includes each file introduced by

SOURCE directives and (on Guardian platforms) HP TACL ASSIGN and DEFINE commands

• Shows the complete name of each file and the date and time when the file was last modified

GLOBALIZED

NOTE: This directive is valid only with the EpTAL compiler.

The GLOBALIZED directive directs the compiler to generate preemptable object code. Preemptable

object code allows named references in a DLL to resolve to externally-defined code and data items

instead of to the DLL’s own internally-defined code and data items. You must specify the GLOBALIZED

directive when compiling code that will be linked into a globalized DLL. By default, the compiler

generates non-preemptable object code. Non-preemptable code is more efficient than preemptable

code and results in faster compilation and execution, so you should specify GLOBALIZED only

when required.

396 Compiler Directives