RE: *NOPASS parameter retaining old value

Oh. That's different. Then I back off and let Bruce's message stand (from
the manual) :

If the unpassed parameter is accessed in the called program or
procedure, unpredictable results will occur.

Sounds like you've proven that point. What more needs to be said?

Dennis Lovelady
http://www.linkedin.com/in/dennislovelady
--
The older I grow the more I distrust the familiar doctrine that age brings
wisdom.
-- H. L. Mencken, Prejudices, Third Series,1922

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-
bounces@xxxxxxxxxxxx] On Behalf Of Rick.Chevalier@xxxxxxxxxxxxxxx
Sent: Wednesday, January 27, 2010 12:31 PM
To: rpg400-l@xxxxxxxxxxxx
Subject: RE: *NOPASS parameter retaining old value

The code works fine. What I don't understand is why ForceRead has a
value. When I run in debug I would expect the evaluation of the
ForceRead parameter to not be addressable because it wasn't passed.
Instead it contains the value from an earlier call that did pass the
parameter. Is it that once the parameter is passed the procedure
retains that address in memory and therefore the value of that
parameter?


-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-
bounces@xxxxxxxxxxxx] On Behalf Of Dennis Lovelady
Sent: Wednesday, January 27, 2010 10:53 AM
To: 'RPG programming on the IBM i / System i'
Subject: RE: *NOPASS parameter retaining old value

If (PreviousBank <> Bank or PreviousLoan <> LoanNumber) or (%Parms

3 and ForceRead);

As Bruce mentions, that's the wrong way to use *NOPASS.

You need

if %parms() > 3;
wForceRead = ForceRead;
else;
wForceRead = *OFF;
endif;

Sorry, but I don't see any problem with the OP use of
ForceRead. %Parms being less that 3 trumps the test for ForceRead (and
the rest of the IF statement). Or doesn't it? Are we saying
that %Parms is unreliable, or that the test order will not be followed?
Both sound wrong to me.

Dennis Lovelady
http://www.linkedin.com/in/dennislovelady
--
... CAUTION!!! Do NOT look at laser with remaining eye.



--
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.



Privileged and Confidential. This e-mail, and any attachments there to,
is intended only for use by the addressee(s) named herein and may
contain privileged or confidential information. If you have received
this e-mail in error, please notify me immediately by a return e-mail
and delete this e-mail. You are hereby notified that any dissemination,
distribution or copying of this e-mail and/or any attachments thereto,
is strictly prohibited.
--
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.