If a procedure creates a stem, and reutrns it to the
code calling the proceudure, then SysDumpVariables is
called after the stem is returned, SysDumpVariables
shows the name of the stem per the proceudre, not the
name it was received as in the general code. This is
confusing when the main code needs several stems
created by the same procedure as SysDumpVariables shows
them all as the same stem name - UUUGGG!!! ;-)
ORexx 2.1.3 on Win32 and 2.3.4.0-4_i386
See the attached sample code for the concise
description of the problem.
Anonymous
Example of error
SysDumpVariables is doing the correct thing. From the standpoint of the place where it the routine is called, it sees a stem with the locat name, not the name of the stem variable that is also referencing the same stem object in the calling context. SysDumpVariables only knows about the variables as they exist in the calling context, and in fact, the stem object referenced by the local variable need not even have been created from a stem variable in the first place.
Reopening this in the light of the behavior that was fixed with the NOVALUE reporting. This really should be returning the variable names, not the stem object names the variables are getting mapped to.
Committed revision 6557.
I believe this one looks resolved in 4.2.0 RC testing. Do you agree, Rick?