|
Ummm... I've written RPG programs that accept "optional parameters" even back when we were stuck with the OPM languages... It doesn't check the parameters at compile time. We didn't have the handy %parms BIF, and had to check something from the PSDS, but it worked... Also, you CAN use OPTIONS(*NOPASS) on programs just like you can on procedures. On Mon, 18 Nov 2002, Bob Cozzi wrote: > > With procedures you do get the advantage of the keyword OPTIONS(*NOPASS) > that allows a parameter to be left off of the parameter list. But if you > do not use that keyword, the compiler does parameter checking at compile > time, requiring you to specify the parameter, thus allowing you to avoid > a runtime error. > > FYI, you can also use this type of thing when calling programs so this > advantage as it relates to procedures isn't there. >
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
