Previous: PtInit updates for Monoprogram form
Up: PtInit updates for Monoprogram form
Next: Setting up Full Re-Initialization
Previous Page: PtInit updates for Monoprogram form
Next Page: Setting up Full Re-Initialization

New Compilation Flags

The following conditional compilation flags have been added, often in conjoint logic with pre-existing flags, to select the environment logistics that Ports assumes. Note that ``undefined'' means explicitly stated to be so by Turbo Pascal's $UNDEF <name> directive. The name should never simply be omitted from mention.

MultiDisc:
Undefined in the present version, its setting should always be opposite to those for monoprogram form. It should be defined if multiple-program form is used, and the programs don't all fit on one disc. This causes Ports to require the application CHAINER.EXE (and its keyed file) to be included on each release disc.
HasLongJump:
Defined if a working routine is available to let Ports emulate non-global EXIT, by jumping out of the dialogue, or to a defined global location outside the module.
UseInterProgComm:
Defined if the IPC unit (InterProgramCommunications) or other reliable means of saving communicated parameters in memory, is to be used for saving long-term parameters between successive modules.
UniProg:
Defined if Ports is to be used in a single unified program of all the activies in the dialogue (was unfortunately named before the term monoprogram came into use). Its setting should always be the opposite of MultiDisc, above.
AllowDlgQuit:
Defined if Extra Services is to include an option to quit the whole dialogue, rather than just the current activity; the latter was always the format used under the p-System.



Previous: PtInit updates for Monoprogram form
Up: PtInit updates for Monoprogram form
Next: Setting up Full Re-Initialization
Previous Page: PtInit updates for Monoprogram form
Next Page: Setting up Full Re-Initialization

Educational Technology Center
Dept. of Info. and Comp.Sci.
Univ. of California, Irvine
92717, CA, USA