On Sun, 13 May 2018 19:16:36 +0000, Seymour J Metz <[email protected]> wrote:
>OOREXX solves many of the problems in classic REXX. > >I never found writing REXX function packages to be difficult. > THere's a lack of closure. Why can't a command (ADDRESS) environment be implemented in Rexx? On Sun, 13 May 2018 19:59:59 +0000, Seymour J Metz <[email protected]> wrote: >All symbols are case insensitive. Talis are case sensivtive: > > bar='baz' > say f.bar > say foo.BAR > say FOO.bar > say FOO.BAR > >will give 4 identical outputs, but change that first line to bar='BAZ' and >you're talking about a different variable. > >You can use the value BIF to get expressions in tails: x =value('foo.'bar'2') > Circuitous. And if BAR || '2' is an assigned variable you may get undesired results. (Try it; I think we had this discusion long ago.) For safety, you need to: TAIL = bar'2' X = foo.TAIL >WTF is a "longITERATE" or a "longLEAVE"? > Idiosyncratic neologism by analogy to "longjump". Imagine ITERATE X or LEAVE X where X is not local but EXPOSEd from an enclosing procedure. >Admittedly I use here documents in Perl, but I'm not a big fan of them. > How about in JCL? >Why can't IBM implement GLOBALV in TSO? > Circuitous. Why not some sort of IMPORT list or EXPOSE list so the names could just be used as variables. As in POSIX shell. >If IBM would be up OOREXX some of your other issues would be addressed. -- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
