|
Gesh, I think I've had everything bass ackwards all this time? I use CONST all the time and never use VALUE unless it's a routine I borrowed from this list or the RPGIV list! -----Original Message----- From: Joel Cochran [mailto:jrc@xxxxxxxxxx] Sent: Thursday, August 07, 2003 4:39 PM To: RPG programming on the AS400 / iSeries Subject: Re: Value vs. Const One caveat that Barbara Morris pointed out to me is that using "value" and "options(*nopass)" on the same variable can be dangerous. If you want a variable to be *nopass and still take advantage of the VALUE benefits, then use CONST... // This is a no-no... d myProto pr d parm1 1a value d parm2 10a value varying d parm3 10a value varying options(*nopass) // 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.
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
