I may not understand what you are saying, but it is my understanding that if
you use a d-spec in your procedure to define a variable then the variable is
local to the procedure.
Paul
-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx]
On Behalf Of Sam_L
Sent: Monday, April 29, 2013 5:31 PM
To: RPG programming on the IBM i (AS/400 and iSeries)
Subject: Re: Procedure PR/PI question
I would like to have an option that says "All the variables I define in
this procedure are local unless I specify otherwise". I know, if I put
it in a separate source file I get the same effect, but this isn't always
practical or politically acceptable in some shops.
Sam
On 4/29/2013 10:37 AM, DeLong, Eric wrote:
Aliasing problems? I'm sure I must just be dense, but huh?!?
CONST is just fine, nearly perfect for most conditions. I can only
imagine a few cases where you could have problems, and all of those are the
result of not keeping the prototype member and the Procedure Interface
maintained properly.
Passing by value? This really makes no sense, since RPG is optimized to
pass by reference. Also, since the OP mentioned this to be a EXTERNAL
PROGRAM prototype, you're still out of luck with VALUE since programs ONLY
accept parms by reference...
--
This is the RPG programming on the IBM i (AS/400 and iSeries) (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.
As an Amazon Associate we earn from qualifying purchases.