Re: Passed by Reference vs. Passed by Value

[Charles Wilt <charles.wilt@xxxxxxxxx>]

If you actually had a PI/PR for a program with VALUE, you should have
gotten a compile time error.

Charles

On Wed, Mar 11, 2020 at 3:26 PM Kevin Wright <kevin.wright@xxxxxxxxxxxx>
wrote:

> Jon? wrote:
> In which case, the variabkle is copied to a new location and *pointer to
>  new location* is passed to procedure.
>  In the end, you always passed a pointer under covert...
>
> Dave wrote:
>         I used to think that.  But then I ran into the situation where one
>
> program was passing a parameter by reference (by default) but the called
> program expected the parameter to be passed by value (explicitly) and the
> called program couldn't see the passed value at all.  Explain to me why is
>
> that?  Thanks for the education.
>
> I (Kevin) write:
> A *program* *always* receives its parameters by reference.
> A *procedure* can receive its parameters either by value or by reference.
> If it is expecting by value but actually gets by reference then what
> occurs is probably undefined. There must be a mismatch between the caller
> and the called, ie "lying" to the compiler / binder at one point or the
> other.
>
> Hope this helps.
>
> Kevin Wright
> --
> This is the RPG programming on IBM i (RPG400-L) mailing list
> To post a message email: RPG400-L@xxxxxxxxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: https://lists.midrange.com/mailman/listinfo/rpg400-l
> or email: RPG400-L-request@xxxxxxxxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at https://archive.midrange.com/rpg400-l.
>
> Please contact support@xxxxxxxxxxxx for any subscription related
> questions.
>
> Help support midrange.com by shopping at amazon.com with our affiliate
> link: https://amazon.midrange.com