It's optional in PL/I as well unless you have a name on the END..
-- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 ________________________________________ From: IBM Mainframe Discussion List [[email protected]] on behalf of René Jansen [[email protected]] Sent: Wednesday, March 29, 2023 11:20 AM To: [email protected] Subject: Re: Stop the ragging on COBOL please [was: RE: ASM call by value] As NetRexx does; but the label is optional. > On 29 Mar 2023, at 17:18, Seymour J Metz <[email protected]> wrote: > >> It's precious that Rexx allows identifying the END by naming the control >> variable. >> Does PL/I do likewise? > > No, PL/I does it better; a name on the end must match the label on the > opening statement.You can have multiple DO loops in the same scope, but PL/I > requires labels to be unique. > > > -- > Shmuel (Seymour J.) Metz > http://mason.gmu.edu/~smetz3 > > ________________________________________ > From: IBM Mainframe Discussion List [[email protected]] on behalf of > Paul Gilmartin [[email protected]] > Sent: Wednesday, March 29, 2023 9:29 AM > To: [email protected] > Subject: Re: Stop the ragging on COBOL please [was: RE: ASM call by value] > > On Wed, 29 Mar 2023 08:13:11 -0500, Joe Monk wrote: > >> "Too many languages lack ELSEIF and strong closure. Fie on >> the danglig ELSE!" >> >> Now you know why COBOL programmers always indented their code ... it helps >> > Past tense? No longer? > >> line up the IF...ELSE structure. That was of course before VS COBOL II >> (Cobol '85). >> > I understand that Python goes even further: it enforces the indention. > > It's precious that Rexx allows identifying the END by naming the control > variable. > Does PL/I do likewise? At times I use an otiose control variable merely so I > can mark the END. > > And it's a shame that JCL doesn't require that the name fields of ELSE and > ENDIF > match that of the IF. > > -- > 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 ---------------------------------------------------------------------- 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
