|
> // This is a no-no... > d myProto pr > d parm1 1a value > d parm2 10a value varying > d parm3 10a value varying options(*nopass) Why is this a no-no? > // Do this instead... > d myProto pr > d parm1 1a value > d parm2 10a value varying > d parm3 10a const varying options(*nopass) > > Now you should use a local variable with a default value, and populate > it with the parm3 value only if %parms() indicates it was passed. That is what I mostly do, but what has that got to do with using CONST or VALUE? Joep Beckeringh
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.