Re: Another ILE question

[Jon Paris <Jon.Paris@xxxxxxxxxxxxxx>]

On 16-Nov-07, at 3:01 AM, rpg400-l-request@xxxxxxxxxxxx wrote:

> But if he had used the VALUE keyword instead of CONST, SRefNo would  
> not
> have been changed with the - second - read.

True - VALUE always makes a copy of the variable.  However it can  
only be applied to procedure calls.

> Kurt Anderson pointed out, the value of a const parameter can be  
> changed
> by directly referencing a global variable.

The value of a global variable can be changed from within a  
subprocedure period.  The CONST bit is a red herring in this case.

> Which is a behaviour of CONST, pass by reference....

Yes - but as I and others have also pointed out - the danger of CONST  
is that the _real_ reference is passed when the size/type match  
exactly.  That is why I would like a COPY option.

Jon Paris

www.Partner400.com
www.SystemiDeveloper.com