Dave, and Barbara, I thought I was following this thread, but now
I am confused and have a question:
Earlier, Joe stated:
"By specifying CONST you specifically told the compiler to ignore any
data past the 40A; in effect, you asked it to do a MOVEL (or EVAL) of
your 100A into a temporary 40A field and call with it."
I >think< that means the parameter passed would be more like "by value"
because the called program has no >reference< to the 40A memory.
If "by constant reference", works as described above, why is the word
>reference< used ?
Thanks in advance!
-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Barbara Morris
Sent: Wednesday, March 28, 2012 5:17 AM
To: rpg400-l@xxxxxxxxxxxx
Subject: Re: passing parameters longer than expected
On 3/28/2012 6:03 AM, Dave wrote:
Le 27 mars 2012 23:44, Barbara Morris<bmorris@xxxxxxxxxx> a écrit :
For a prototyped parameter passed by reference (no CONST or VALUE),
Err.. doesn't CONST mean passed by reference?
Yes, technically. But the manual refers to that as "by constant reference".
--
Barbara
--
This is the RPG programming on the IBM i / System i (RPG400-L) mailing list To post a message email: RPG400-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at
http://archive.midrange.com/rpg400-l.
midrange.com
