Re: AW: PL/I and optional parameters
The name of the program is ESCHATON, and irrespective of the number or value of parameters passed, always returns 42. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: AW: PL/I and optional parameters
> I have a PL/I subroutine call that has 297 optional parameters. That is the > function has a parameter list with up to 100 tuples of parameters. The first > tuple is required, and tuple 2 through 100 are optional. OK, I've been watching this thread with growing curiosity and I can't stand it any longer: What in the world are you doing with a subroutine with that many parameters? Is the code that calls this routine machine-generated? I can't imagine a human being coding such a call. -- Jerry -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
AW: Re: AW: PL/I and optional parameters
> The earlier post by Peter Hunkeler was referring to the LIST attribute of > ENTRY, described here: > http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/IBM3LR60/6.10.5 Yep, this is what I referred to. -- Peter Hunkeler -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: AW: PL/I and optional parameters
On Wed, 4 Nov 2015 11:40:34 -0600, Jon Butler wrote: >LIST has been part of PL/I, and most high-level languages, since at least the >370...that's a far back as I go! > >You can use LIST to get an listing of the assembler generated by the PL/I >statements in your module. You can also limit the output by using a LIST(n,m) >where n and m are the line numbers in your program for which you want the >assembler to be shown. These are the actual line numbers used by the >compiler, not the editor line numbers. > >If you use LIST, you many not want to use OPTIMIZE, so you see the assembler >in the same order as your code before the optimizer re-arranges it. You are referring to the LIST compiler option described here: http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/IBM3PG80/1.1.1.48 The earlier post by Peter Hunkeler was referring to the LIST attribute of ENTRY, described here: http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/IBM3LR60/6.10.5 Bill -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: AW: PL/I and optional parameters
LIST has been part of PL/I, and most high-level languages, since at least the 370...that's a far back as I go! You can use LIST to get an listing of the assembler generated by the PL/I statements in your module. You can also limit the output by using a LIST(n,m) where n and m are the line numbers in your program for which you want the assembler to be shown. These are the actual line numbers used by the compiler, not the editor line numbers. If you use LIST, you many not want to use OPTIMIZE, so you see the assembler in the same order as your code before the optimizer re-arranges it. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
AW: PL/I and optional parameters
> I have a PL/I subroutine call that has 297 optional parameters. That is the > function has a parameter list with up to 100 tuples of parameters. The first > tuple is required, and tuple 2 through 100 are optional. [snip] > Is there a shorter way of declaring 297 optional parameters in PL/I? You may want to look at the "LIST attribute" of an ENTRY declaration in the Enterprise PL/1 Language Reference. It might require the Enterprise edition of the complier, I'm not sure it was supported on elder versions of the comiler. There are builtin funrctions that help you find how many optionals have been specified and where they are. -- Peter Hunkeler -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN