RE: Callp question

Call me idealistic, but I believe the intent of a procedure is to do one
thing only. The purpose of parameters is to supply values upon which the
procedure operates, not to specify a switch which alters the function
performed.

On the other hand, I well know that creating four procedures where one
will do can also multiply the overhead of documentation, especially if
you use change management software.

I think the deciding factor would be how much difference there was
between the functions, which if your three procedures are all calling
the same procedure anyway would seem to be small.

Trevor Briggs
Analyst/Programmer
Lincare, Inc.
(727) 431-1246
TBriggs2@xxxxxxxxxxx
-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Dave
Sent: Monday, August 06, 2012 7:49 AM
To: RPG programming on the IBM i / System i
Subject: Callp question

Hi,


I'm being asked to do this :

DoStuffThisWay ();

DoStuffTheOtherWay ();

DoStuffTheOldWay()

Instead of having : DoStuff (wayToDoStuff); So that the caller does
not care about the parameter.

Then, in the module containing my 3 procedures :

P DoStuffThisWay

DoStuff(1);

DoStuffTheOtherWay

DoStuff(2);


Etc.

Obviously,this means maintaining more procedures and duplicating code.
I was wondering about procedure pointers. Could that help? How? Any
other ideas?

Thanks.