CompuServe Thread

Mike, One of my other customers sent me that example code as well. The examples dealing with variable scoping in procedures (with and without expose) are simply the way REXX is defined. The example dealing with compound variables is again the way REXX is defined — when compound variables are expanded, only simple variables are substituted into the compound name. Apparently the author of the example doesn't like this behavior, but it isn't a problem with the ARexx implementation. The example with parse value value() looks like a bug, though I'll have to check further. Since the VALUE symbol is a keyword in the context, ARexx disallows subsequent use of the symbol VALUE. -Bill Hawes