Hardware Reference
In-Depth Information
Figure 4.8
Example of commented source code showing program header
information. The code is written in Visual Basic and is being edited using the
EditPlus editor
•
Names of other modules, subroutines, or macros on which the module
depends and, where applicable, names of relevant macro libraries in which
definitions are held.
•
Entry requirements (in terms of register and/or buffer contents before the
module is executed).
•
Exit conditions (in terms of register contents, buffers, and flags after the
module has been executed).
•
In the case of assembly language modules, a list of registers used during exe-
cution of the code (which may have their contents changed as a consequence).
When producing a program header, it is wise to include any information
which may be required by another programmer who may subsequently need to
