You know what I think would “really be nice”? A call/function/mechanism that would permit an externally called exec to gain access to the calling exec’s ENVB/environment. Perhaps it should be a 2-way street and not “automatic” but a facility in one exec to authorize access, and a facility in the ‘other’ exec to set up the access. Why? Because it would permit an external called exec to access and set variables in the other exec. So finally, it would, among other things, become “easy” to pass entire complex variable structures back and forth between a “parent” and an externally called “child”. That’s something I’m already doing in my own code, passing “stems” back and forth, but my solution for doing it, although it works, is pretty ugly. One exec builds semicolon delimited set of “stem.variable=value;” statements and passes it as a string to the “other side” which then gets executed by way of “interpret”. It works, but like I said, it’s ugly.
Sure would be nice to have, on all platforms, in all versions of REXX.
_______________________________________________ Oorexx-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/oorexx-devel
