Re: Another ILE question : CONST vs VALUE

Hi Tom -

On Thu, 15 Nov 2007 15:21:44 -0600, "Armbruster, Tom"
<Tom.Armbruster@xxxxxxxxxxxxxxx> wrote:

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?

CONST doesn't always require a temporary variable. If a single field
(rather than a constant or an expression) is specified on the call and
the length and type match the prototype, there is no need for a
temporary variable.

If there is no temporary variable, and if the field on the call is
global, and if that global field is changed within the procedure, then
the value of the procedure parameter field will also change because
it's the same memory area.

It would be good if there were a keyword that could be used along with
CONST, or as a replacement for CONST, which would force a temporary
variable to always be used.

Ken
Opinions expressed are my own and do not necessarily represent the views
of my employer or anyone in their right mind.