[<<Previous Entry] [^^Up^^] [Next Entry>>] [Menu] [About The Guide]
+--------------------------------------------------------------------------+
| Technical Notes |
+--------------------------------------------------------------------------+
Only subroutines, procedures, and functions that are returned from may be
overlaid.
+--------------------------------------------------------------------------+
| Assembly Language Programmers: |
+--------------------------------------------------------------------------+
both near and far calls are allowed. No jumps or GOTO's to overlays in any
stack language, and don't play games with the stack's return addresses.
The overlay manager overlay:manager assumes everything is returned from,
so it stores the calling address on its internal stack. You should make
sure that all CODE class segment names end in CODE. If you use another
name, link with the /oc option.
Brackets ("[","]") can be used instead of parentheses to indicate
overlays. This causes WarpLink to act differently than when
parenetheses are used. When brackets are used, calls from an overlay
to the root are vectored. This can sometimes cause a speed degradation,
but it will not be noticed in most cases. Brackets also allow an overlay
directly calling the root to be safely swapped out by other overlays
before the calling overlay is returned to.
If you are using small code model overlays, brackets must be used instead
of parentheses to specify overlays. The program will not work unless the
brackets are used.
Make sure you link OVLMGR.OBJ into the root it contains the runtime
overlay manager. It cannot be overlaid.
Do not place startup code in an overlay.
Functions which perform indirect near calls cannot be overlaid.
NOTE: WarpLink only creates one .OVL file for your application.
Online resources provided by: http://www.ClipX.Net --- NG 2 HTML conversion by Dave Pearson