National Instruments AutoCode NI MATRIX - Manual (Page 237)

Chapter 9 Global Scope Signals and Parameterless Procedures
AutoCode Reference 9-10 ni.com
Analyzer and AutoCode Warnings
The Analyzer reports questionable connectivities or situations regarding
usage of the Global Scope signals. Also, AutoCode might report additional
warnings during code generation. Evaluate these warnings and verify that
the generated code is what you expect. You might need to change your
model to fix the situation.
Changing Scope Class
To properly match Global Scope signals for parameterless procedures,
you might need to use an explicit copy to resolve the naming. This is
accomplished by using a unit-gain block—that is, a gain block with a gain
factor of 1. Using the gain block in this way will let you match any
connectivity that you require. You might want to use a custom icon for this
usage of the gain block to provide a better graphical representation of the
copy instead of a gain.
Command Options
The following command options force the scope of block outputs:
• -nogscope —This option forces all Output Scopes to be Local for all
block outputs. Connection to a Input Scope that is Global results in a
copy into the global variable before the procedure call.
• -allgscope —This option forces all Output Scopes to be Global for
all block outputs while Input Scopes are forced to Local, thus disabling
parameterless procedures.