Re: *NOPASS parameter retaining old value

Technically, there isn't a problem in this instance...as long as the
compiler does short circuit evaluations...

But IMO, it's a "best practice" if you will to have the check for
*NOPASS parms explicitly set working copies of the data that are then
used in the actual business logic.


Charles



On Wed, Jan 27, 2010 at 11:52 AM, Dennis Lovelady <iseries@xxxxxxxxxxxx> wrote:

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.