Why would the CONST value change outside of the procedure during a call,
and why would it matter? The CONST value is for processing at the time
of the call, so even if the value were say a timestamp, it would be the
value at the time of the call. Can someone provide an example as to
when a constant value provided to a program would be altered during the
called procedure and what effect it might have?
Tom Armbruster
Systems Integration Manager
Travelocity On Location
tom.armbruster@xxxxxxxxxxxxxxx
http://www.showtickets.com
-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Kurt Anderson
Sent: Thursday, November 15, 2007 12:58 PM
To: RPG programming on the AS400 / iSeries
Subject: RE: Another ILE question : CONST vs VALUE
Hey David,
Something I came across in the WDSC RPG Const help. Take particular
notice of the last part of the last sentence, which is exactly what you
experienced.
"Attention!
Do not use this keyword on a prototype definition unless you are sure
that the parameter will not be changed by the called program or
procedure.
If the called program or procedure is compiled using a procedure
interface with the same prototype, you do not have to worry about this,
since the compiler will check this for you.
Although a CONST parameter cannot be changed by statements within the
procedure, the value may be changed as a result of statements outside of
the procedure, or by directly referencing a global variable."
Kurt Anderson
Application Developer
Highsmith Inc
-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of David FOXWELL
Sent: Thursday, November 15, 2007 8:51 AM
To: RPG400-L@xxxxxxxxxxxx
Subject: RE: Another ILE question : CONST vs VALUE
midrange.com
