To be honest, every programming language or scripting languages have pros and cons. Except for Java, I kid .....
On Fri, Jan 11, 2019 at 5:09 PM scott Ford <[email protected]> wrote: > Wow, boys .....I been at it 40+ yrs and after awhile it all runs together > ... > > > > On Fri, Jan 11, 2019 at 4:57 PM Seymour J Metz <[email protected]> wrote: > >> > I'd much prefer that Rexx provide instream data, with symbol >> substitution, >> >> DATA ... END and DATA PROMPT ... END are very useful, much more useful >> than here documents, IMHO. >> >> >I eschew STACK with any command that provides STEM as an alternative. >> >> STEM is nice for commands that support it, but most commands do not. >> >> > I'm phobic that a rogue subroutine will corrupt my stack, or even >> DESBUF. >> >> That's harder than you might think; DESBUF only trashes stacks that REXX >> created. >> >> > STACK is a crude circumvention for overly restrictive variable scoping. >> >> No. You might certainly use it that way, but I find that a good >> screwdriver makes a bad hammer, and vice versa. >> >> -- >> Shmuel (Seymour J.) Metz >> http://mason.gmu.edu/~smetz3 >> >> ________________________________________ >> From: IBM Mainframe Discussion List <[email protected]> on behalf >> of Paul Gilmartin <[email protected]> >> Sent: Friday, January 11, 2019 4:39 PM >> To: [email protected] >> Subject: Re: Unreadable code (Was: Concurrent Server Task Dispatch issue >> multitasking issue) >> >> On Fri, 11 Jan 2019 21:15:20 +0000, Seymour J Metz wrote: >> >> >> It's there, and other implementations of Rexx, such as Regina, >> struggle to emulate it. >> > >> >All implementations of REXX provide a stack, but none of them even try >> to provide the stack mechanisms that TSO has and CLIST DATA/DATA PROMPT >> support. >> > >> I'd much prefer that Rexx provide instream data, with symbol >> substitution, >> as POSIX shell and even JCL do. >> >> I eschew STACK with any command that provides STEM as an alternative. >> I'm phobic that a rogue subroutine will corrupt my stack, or even DESBUF. >> >> I applaud ADDRESS SYSCALL for relying on STEM, never (AFAIK?) STACK. >> >> STACK is a crude circumvention for overly restrictive variable scoping. >> CMS Piplines has YA chaotic circumvention. >> >> -- gil >> >> ---------------------------------------------------------------------- >> For IBM-MAIN subscribe / signoff / archive access instructions, >> send email to [email protected] with the message: INFO IBM-MAIN >> >> ---------------------------------------------------------------------- >> For IBM-MAIN subscribe / signoff / archive access instructions, >> send email to [email protected] with the message: INFO IBM-MAIN >> > -- > Scott Ford > IDMWORKS > z/OS Development > -- Scott Ford IDMWORKS z/OS Development ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
