pTAL Conversion Guide

Compiler Operation
pTAL Conversion Guide—527302-002
19-6
For pTAL and TAL
For pTAL and TAL
All compiler directives in Table 19-2 on page 19-6 belong to pTAL, and some also
belong to TAL:
Table 19-2 on page 19-6 applies to all forms of each directive:
Status in pTAL Meaning For more information:
Unchanged Directive is the same in pTAL and TAL
(except for the minor syntax change
explained in the following Note)
pTAL Reference Manual
or TAL Reference Manual
Changed Directive is different in pTAL and TAL Table 19-3
on page 19-8
New Directive belongs only to pTAL (the
TAL compiler ignores it)
New Directives
on page 19-11
Example Applies to:
FMAP
•
FMAP
•
NOFMAP
DEFEXPAND
•
DEFEXPAND
•
NODEFEXPAND
•
PUSHDEFEXPAND
•
POPDEFEXPAND
Note. In pTAL, a directive that begins with “NO”, “PUSH”, or “POP” can have a space after
“NO”, “PUSH”, or “POP”; in TAL, it cannot. For example, “NO FMAP” and “PUSH
DEFEXPAND” are syntactically correct in pTAL, but not in TAL. “NOFMAP” and
“PUSHDEFEXPAND” are syntactically correct in both pTAL and TAL.
Exception: “NOCALL_SHARED” cannot be spelled “NO CALL_SHARED”.
Table 19-2. pTAL Compiler Directives (page 1 of 3)
Unchanged in pTAL Changed in pTAL New in pTAL
ASSERTION
BEGINCOMPILATION
1
BLOCKGLOBALS
CALL_SHARED
3
CHECKSHIFTCOUNT
COLUMNS
DEFEXPAND
DEFINETOG
DO_TNS_SYNTAX
1. The EpTAL compiler ignores this directive.
2. The EpTAL compiler does not accept this directive.
3. The pTAL and EpTAL compilers treat this directive differently—for details, see the pTAL Reference Manual.