RE: Procedure Parameter Change (was Exported Variables)

Thanks for posting the article. 

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Joel Cochran
Sent: Tuesday, January 11, 2005 11:57 AM
To: RPG programming on the AS400 / iSeries
Subject: Re: Procedure Parameter Change (was Exported Variables)

Kurt,

> My thought is: modify the procedure to be 3A instead of 1A (which I 
> think you're saying is wrong, or more prone to problems).
> 
> Me: modify ProcA to reflect the new field length, potentially modify 
> programs that call this procedure, and recompile programs that use the

> module this procedure is in.
> 
> You (again, from my understanding): create ProcB to reflect the new 
> field length, recompile programs that use the module this procedure is

> in.  Write code around ProcA to catch and send an error when 
> attempting to pass ProcA a value greater than it can accept... Or 
> check the value of the code field and move it into a 1a field (if the 
> one [code_likeFldA] in the proc call is defined with Like(FldA)) and 
> call ProcA, else call ProcB.

Sorry I'm coming late to the party, but changing the parameters of an
existing exported sub-procedure is a very bad idea.

Sorry i don't have more time to explain, but I do have an article that
may help a bit.  It also discusses an approach I use called "Dual
Prototyping" to help manage exactly this kind of change:

http://www.itjungle.com/fhg/fhg051204-story03.html

HTH,

Joel Cochran
http://www.rpgnext.com

--
This is the RPG programming on the AS400 / 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.