TAL Programmer's Guide

Binding Object Files
Compiling Programs
14–6 096254 Tandem Computers Incorporated
Binding can take place:
During a compilation session
After a compilation session
At run time (library binding)
Binding During
Compilation
During compilation, BINSERV constructs a master search list of object files from
SEARCH directives in the source file. After a successful compilation, BINSERV binds
into the new object file any procedures from object files listed in the master search list
that resolve external references.
You can do further binding on the object file produced by BINSERV by using Binder
or the operating system.
Binding After Compilation After compilation, you can bind object files interactively by using Binder as described
in the Binder Manual. For example, you can build a target file from separate object
files, display the content of object files, reorder target-file code blocks, produce
optional load maps and cross-reference listings, specify a user run-time library, and
modify the content of named global data blocks and code blocks in the target file.
Binding at Run Time You can build a library of procedures to share at run time among applications or to
extend an application’s code space. At run time, the operating system binds the
library file to the program file. You store the run-time library in a separate file, and
then associate the library file with your object file by using any of the following
methods:
A LIBRARY directive in the source file
The Binder SET LIBRARY command, described in the Binder Manual
The TACL RUN LIB command, described in the TACL Reference Manual
The LIBRARY directive lets you specify a user library to search before searching the
system library for satisfying external references. LIBRARY can appear anywhere on
the compilation command or in the source code:
!Lots of code
?LIBRARY mylib
!More code