HP 3000 Manuals HP 3000 Manuals
RLFILE
RLFILE is a System-Dependent MPE/iX Option.
When the RLFILE compiler option is ON, every level-one routine goes into
its own object module in the RL file. (Routines nested within level-one
routines go into the same object module as the level-one routine in which
they are nested.)
Syntax
$RLFILE {ON }$
{OFF}
Default OFF.
Location At front.
When RLFILE is OFF (the default), the entire compilation unit goes into
one object file. If the object file is an existing RL file, the entire
compilation is placed into it. If the object file is an existing NMOBJ
file, the object file is rewritten. If the object file is neither an RL
nor an NMOBJ file, an error occurs. If the object file does not exist,
the system creates an NMOBJ file with the specified name.
When RLFILE is ON, the compilation unit goes into an RL file procedure by
procedure. This allows procedural-level manipulation similar to that on
MPE V. An error occurs if the object file exists, but is not an RL file
(that is, if it is an NMOBJ file). If the object file is an existing RL
file, object modules replace existing modules in the RL file. If the
object file does not exist, an RL file is created with the specified
name.
When RLFILE is ON, the RL file can be significantly larger than if the
program were compiled into an NMOBJ file, due to the duplicate
information in each level-one object module. If SYMDEBUG is also ON, the
RL file is even larger, because debug information is duplicated in each
level-one object module if a local variable is declared using a global
type.
Example
$RLFILE ON$
PROGRAM prog;
.
.
.
NOTE If you use Pascal modules, all procedures and data in a particular
module are put into one object module.