Barbara,
there was sometime a bug when passing parameters with constant reference.
If I try to change a parameter passed with constant reference, it cannot be
changed with an EVAL statement in the called procedure, I get a compile
error.
If I try to clear the same parameter with the OpCode CLEAR, it get compiled
and even worse it really get cleared and if no temporary parameter is
created it is returned to the caller.
Do you know if it is corrected? PTF?
Mit freundlichen Grüßen / Best regards
Birgitta Hauser
"Shoot for the moon, even if you miss, you'll land among the stars." (Les
Brown)
"If you think education is expensive, try ignorance." (Derek Bok)
"What is worse than training your staff and losing them? Not training them
and keeping them!"
-----Ursprüngliche Nachricht-----
Von: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx] Im
Auftrag von Barbara Morris
Gesendet: Thursday, 29. January 2009 02:43
An: rpg400-l@xxxxxxxxxxxx
Betreff: Re: CONST and VALUE revisited
rob@xxxxxxxxx wrote:
That article made no mention of how the const can be inadvertently
modified. In fact, it leads us to believe that is not a possibility.
There's one way a CONST parameter can be changed while the procedure is
running. If you pass a global variable by CONST to a subprocedure in
the same module, and the subprocedure modifies the global variable
directly, then the value of the CONST parameter may reflect the change.
It would depend on whether the compiler had passed the global vairable
directly or whether it had used a temporary.
midrange.com
