Table of Contents
Advertisement
Getting Started
17
Modules, Routines, and Such
There are three basic activities associated with using assembled modules and routines. First,
there is the need to retrieve them from wherever they may be stored (including providing a
place for them to be kept while they are resident in the memory of the machine). Second, there
is the actual execution of the routines. And third, there is the occasional requirement to store,
or re-store a module on mass storage (including, perhaps, the need to free up the space in
memory it previously occupied).
Names
Routines, modules, and files all have names. The names given them mayor may not bear some
significance to one another; that depends upon you and the way that you name things.
Conventions for the naming of files and methods of general file manipulation can be found in
the Operating and Programming Manual and in the Mass Storage Techniques Manual. The
conventions are not any different than for files in general.
Names for modules are assigned with the creation of the source. In the assembly language
source code, you have a NAM pseudo-instruction. This serves two purposes - to designate the
beginning of the module and to assign the module a name. All of the assembly source state-
ments which follow the NAM are in that module until an END pseudo-instruction is encoun-
tered. Thus, recalling the previous example - .
40
ISOU~£E
NOP
All of the ISOURCE statements between lines 20 and 60 (in this case, just the one) form the
module called "Example". The formal syntaxes of these pseudo-instructions are -
t···~RtYl
{module name}
Et---~D
{module name}
{module name} is a symbol which becomes the name of the module. It follows the same rules as
names in BASIC: up to fifteen characters; starts with a capital letter; followed by only non-
capital letters, numbers, or the underscore character.
Advertisement
Table of Contents
