Apexp (application symbol export) – Echelon Neuron User Manual
Page 144

APEXP (Application Symbol Export)
The APEXP directive is used to export symbols that interface with the Neuron C
application.
An exported symbol must be defined as a label within the assembly file from
which it is exported. Exporting the symbol makes it available to the linker. The
linker uses exported symbols to resolve references from other object modules. It
is possible, and sometimes required, to export and import a symbol within the
same assembly file to permit the linker to resolve expressions between separate
segments.
See also EXPORT (Export Symbol).
Syntax:
The APEXP directive requires either a label or an argument, or both.
label
APEXP
APEXP symbol
APEXP symbol, symbol, ...
label
APEXP symbol
label
APEXP symbol, symbol, ...
An argument can be a symbol, or it can be a list of symbols separated by commas.
The argument specifies the symbols to be exported. If there is no argument for
the directive, it must have a label, and the label becomes the exported symbol. If
there are both an argument and a label, the argument specifies the symbols to be
exported and the label is a standard label.
Examples:
The following example exports the label %IOToggle as an external symbol to the
Neuron C application:
%IOToggle APEXP
The following example exports the symbols Flag1 and Flag2 to the Neuron C
application:
InFlags APEXP Flag1, Flag2
134
Neuron Assembler Directives