.
That is the default situation for a method unless an EXPOSE is used.
Basically, all variables are local unless identified as object scope on the
EXPOSE instruction. USE LOCAL is intended to give you the opposite
situation where all variables are of object scope unless explicitly
identified as local. I've found this particularly desirable in INIT methods
where all of the object variables for an instance need to be initialized.
OK.
If the object is a fairly complex one, you end up with a giant EXPOSE
statement at the beginning to identify each variable to be initialized.
Hmm. I often use:
shared='error rc logfile whatever whatever' -- all the variables only
needed if there is an error
then in the called routine:
procedure expose (shared)
so the list(s) of variable that might be shared are in one place and easily
updated for all routines when one needs to change or add one.
Mike
------------------------------------------------------------------------------
One dashboard for servers and applications across Physical-Virtual-Cloud
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
_______________________________________________
Oorexx-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
