TAL Programmer's Guide

Compiling With Saved Global Data
Compiling Programs
096254 Tandem Computers Incorporated 14–25
Checking the Syntax of Global Data
The following compilation command compiles source file MYPROG but produces no
object file. The SAVEGLOBALS directive saves global declarations in file TALSYM.
The SYNTAX directive checks the syntax of the global declarations:
TAL /IN myprog/; SAVEGLOBALS talsym, SYNTAX
You can then recompile and retrieve the saved global declarations (but not the saved
global initializations, because no object file was produced in the preceding
compilation):
TAL /IN myprog/; USEGLOBALS talsym, SYNTAX
Effects of Other Directives When you use the following directives in the SAVEGLOBALS compilation, they affect
subsequent USEGLOBALS compilations as follows:
Directive in
SAVEGLOBALS
Compilation Effect in Subsequent USEGLOBALS Compilations
SYNTAX Negates the need for using SEARCH in the USEGLOBALS compilation because
no object file was produced by the SAVEGLOBALS compilation
INHIBITXX Continues to inhibit generation of extended indexed instructions for extended
pointers located in the first 64 words of primary global area
INT32INDEX Continues to generate INT(32) indexes from INT indexes
PRINTSYM Continues to print symbols in the listing
SYMBOLS Continues to make symbols available for all data blocks that had symbols during
the SAVEGLOBALS compilation
These directives set the corresponding attribute in ensuing variable declarations. The
compiler saves such information in the SAVEGLOBALS object file along with all the
other information it saves about each variable.