Re: Guaranteeing re-resolution on CALL statements

I was going from memory but I knew somewhere from the dark recesses of
my memory there was a caveat about the optimization.

bvining@xxxxxxxxxxxxxxx 08/12/2009 11:53:01 AM >>>

From the RPG Reference:

When a program reference is made with a variable, its current value is
compared to the value used on the previous program reference operation
that
used that variable. If the value did not change, no resolve is done. If
it
did change, a resolve is done to the new program specified. Note that
this
rule applies only to references using a variable name.

----- Original Message -----
From: "Roger Harman" <RHarman@xxxxxxxxxx>
To: <rpg400-l@xxxxxxxxxxxx>
Sent: Wednesday, August 12, 2009 1:35 PM
Subject: Re: Guaranteeing re-resolution on CALL statements

If you make FOO a variable, it should re-resolve. But... I wonder if
the compiler is smart enough to know that the if the value being moved
to it is always the same (ex. "MYPGM") it may optimize it out?

jamesl@xxxxxxxxxxxxxxxxx 08/12/2009 11:17:35 AM >>>

I have a situation (in an update utility) in which a statement of the
form

C CALL FOO
C PARM BAR
. . .

is called repeatedly for different "elements" of the update. It can,
under certain circumstances, result in FOO itself being replaced,
producing a MCH3402 exception on subsequent iterations.

Anybody know of an easy way to guarantee re-resolution of FOO to the

new

version, if it gets updated?

--
JHHL
(wishing I could ANSWER somebody's question for a change!)
--
This is the RPG programming on the IBM i / System i (RPG400-L) mailing
list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.
--
This is the RPG programming on the IBM i / System i (RPG400-L) mailing

list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.