Re: *NOPASS parameter retaining old value -- RPG400-L

Subject: Re: *NOPASS parameter retaining old value
From: Rory Hewitt <roryhewitt@xxxxxxxxx>
Date: Wed, 27 Jan 2010 09:44:35 -0800
List-archive: <http://archive.midrange.com/rpg400-l>
List-help: <mailto:rpg400-l-request@midrange.com?subject=help>
List-id: RPG programming on the IBM i / System i <rpg400-l.midrange.com>
List-post: <mailto:rpg400-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/rpg400-l>, <mailto:rpg400-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/rpg400-l>, <mailto:rpg400-l-request@midrange.com?subject=unsubscribe>

Yes, that's exactly it. That's why you always need to check whether the parm
was passed *before* you check its value.

On Wed, Jan 27, 2010 at 9:31 AM, <Rick.Chevalier@xxxxxxxxxxxxxxx> wrote:

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?

As an Amazon Associate we earn from qualifying purchases.

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.