Compatibility Issues - National Instruments AutoCode NI MATRIX Reference

© National Instruments Corporation
Task/Procedure
subsystem task 1
subsystem task 2
subsystem task 3
startup procedure 1
startup procedure 2
startup procedure 3
background procedure 1
background procedure 2
interrupt procedure 1
Notice the relative numbering within a task/procedure type. Also, be aware
that standard procedures are not given a unique identifier for the purposes
of the element. A standard procedure SuperBlock uses the id
caller_id
of its caller as its own when the caller's id is needed.
In addition to declaring the extra element in the
option causes AutoCode to assign the unique task/procedure identifier to
the element and to use the
caller_id
variable block callouts for variable block accesses within a standard
procedure SuperBlock. Refer to the
for more information about variable block callouts.

Compatibility Issues

The use of affects all generated procedures. It is not possible to
-epi
specify some procedures with and some other procedures without the
element. Also, subsystem code generated assumes the
caller_id
existence of the
caller_id
structures and generates code based on that assumption.
info
You cannot automatically mix procedures generated with the
and procedures generated without the
the element to the old procedure's
caller_id
The old procedure will have been generated without the existence of the
new element and thus its presence in the structure will not affect the
previously generated code as that code never references it. Its effect,
Chapter 5
Table 5-3. Procedure Ordering
caller_id
Global Variable Block Callouts
element in all standard procedure SuperBlock
-epi
5-19
Generated Code Architecture
Unique Identifier
1
2
3
–4
–5
–6
7
8
9
structure, the
info
as an argument for
-epi
option; you must manually add
structure declaration.
info
AutoCode Reference
-epi
section
option