HP Pascal/iX Reference Manual (31502-90022)

12- 64
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.
RLINIT
RLINIT is a System-Dependent MPE/iX Option.
The RLINIT compiler option initializes an RL file to empty.
Syntax
$RLINIT$
Default None.
Location At front.
The RLINIT compiler option initializes an RL file to empty before placing
any object code in it. If RLINIT is not used, the compiler appends the
new object code to any code that is already in the RL file. If $OLDPASS
is used, or no file with the specified name exists, the system creates an
RL file. If the specified object file is not an RL file (that is, if it
is an NMOBJ file), an error occurs.
S300_EXTNAMES
S300_EXTNAMES is an HP Pascal Option.
The S300_EXTNAMES compiler option specifies that the external names of
procedures in modules are of the form modulename_procedurename .
Syntax
$S300_EXTNAMES {ON }$
{OFF}
Default OFF.
Location Before the EXPORT part of a module.
The S300_EXTNAMES option tells the linker to use the external name