On 6/27/23 11:04:43, Jonathan Scott wrote:
Would any know the difference in scope
Of a local used in open code and a global used
In a macro the both seem to have a scope of the entire assembly
A local variable is unique to the context where it is defined,
so a local variable defined in open code applies to all open
code, and a local variable in a macro is defined only in that
macro. If the same name is used for a local variable in a
different context, it refers to a separate variable.
A global variable is the same variable in all contexts where it
is defined.
Is there a way to declare a symbol in a macro so that it is
visible in the declaring macro and in macros it calls but
not in open code nor in macros calling the declaring macro?
That would mimic the customary behavior of static scope in
block structured languages and POSIX shell "export", but
not quite REXX "PROCEDURE EXPOSE"..
--
gil
