× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  1.  Home
  2. RPG400-L
  3. December 2001

RE: Procedure parameter with VALUE option

Your understanding of VALUE is correct but CONST works differently.  The
compiler won't allow you to change a parameter defined as CONST.  This is
why I prefer CONST, if I mistakenly try to change a parameter thinking the
caller will see the change then the compiler will stop me where VALUE would
allow me to do it and my program won't work as expeceted.

Scott Mildenberger

> -----Original Message-----
> From: jpcarr@tredegar.com [mailto:jpcarr@tredegar.com]
> Sent: Thursday, December 13, 2001 6:51 PM
> To: rpg400-l@midrange.com
> Subject: Re: Procedure parameter with VALUE option
>
> My understanding is if passed by Value and the procedure Does
> modify the
> passed parameter
> the Caller doesn't see the change.    Is that correct?
> Is it also correct for CONST ?

As an Amazon Associate we earn from qualifying purchases.

This thread ...
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.