× 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.


  • Subject: Re: CONST vs. VALUE
  • From: Jon.Paris@xxxxxx
  • Date: Tue, 27 Mar 2001 14:10:42 -0400


 >> What's the difference between using CONST and VALUE on ILE parm lists?

Huge difference.  The RPG Redbook goes into it in more detail but here's
the short version.

CONST is a pass by reference i.e. a pointer is passed just as it would be
if there was no keyword.  The thing that CONST buys you is that if there is
a minor difference in the parm being passed and the proto definition the
compiler takes care of it.  e.g. Proto says 15P 5 parm is 10S 2 - in this
case the compiler generates a 15P 5 temporary field - moves the parm to it,
and passes the temp to the called program/procedure.

VALUE actually passes the _content_ of the field on the stack (not a
pointer).  It deals with differences just as CONST does but it is _always_
a copy of the data that is passed whereas CONST may pass a pointer to the
original field or to a temp.

CONST can be used for both program and procedure calls - VALUE can only be
used when calling procedures (i.e. bound calls)



+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---

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.