TAL Programmer's Guide

Binding Object Files
Compiling Programs
096254 Tandem Computers Incorporated 14–5
Completion Codes
Returned by the Compiler
When the compiler compiles a source file, it either completes the compilation normally
or stops abnormally. It then returns a process-completion code to the TACL product
indicating the status of the compilation. Table 14-1 explains the process-completion
code values.
Table 14-1. Completion Codes
Code Termination Meaning
0 Normal The compiler found no errors or unsuppressed warnings in the source file.
(Warnings suppressed by the NOWARN directive do not count.) The object
file is complete and valid (unless a SYNTAX directive suppressed its
creation).
1 Normal The compiler found at least one unsuppressed warning. (Warnings
suppressed by the NOWARN directive do not count.) The object file is
complete and valid (unless a SYNTAX directive suppressed its creation).
2 Normal The compiler found at least one compilation error and did not create an
object file.
3 Abnormal The compiler exhausted an internal resource such as symbol table space or
could not access an external resource such as a file. The compiler did not
create an object file.
5 Abnormal The compiler discovered a logic error during internal consistency checking
or one of the compiler’s server processes terminated abnormally. The
compiler did not create an object file.
8 Normal The compiler could not use the object file name you specified, so it chose
the name reported in the summary. The object file is complete and valid.
Binding Object Files You can compile source files into interim object files and then use Binder to bind the
interim object files into a new object file, as shown in Figure 14-2.
Figure 14-2. Binding Object Files
New object
file
BINDER
Interim
object file
Interim
object file
Source file
Source file
TAL compiler
TAL compiler
411