RE: Function Opinion

Trued, but putting one procedure, in one module and then creating a service
program with just that one procedure in it, should be a rare exception not a
practice.


Bob Cozzi
Cozzi Consulting
www.rpgiv.com


-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx]
On Behalf Of Andy Holmer
Sent: Wednesday, October 29, 2003 11:43 AM
To: RPG programming on the AS400 / iSeries
Subject: RE: Function Opinion

Joe,

>Pardon my ignorance, but if you are only putting on function per
program,
>why bother making them service programs?

I am not defending the one procedure per service program scheme, but if
you make procedures into service programs then you are binding by
reference.  If you compile the procedure into a module, and then link
the procedure in your CRTPGM, then you are binding by copy.  Then, say
six weeks later someone changes a few lines of code in that widely used
date manipulation procedure (as an example), if it is in a service
program you update the service program and move on with today's
activities.  If that code was copied into 100 programs because you bound
by copy, then you have a lot of UPDPGM statements ahead of you.  A good
rule of thumb is to put any procedure that is used by more than one
program into a service program.

HTH,                    
Andy Holmer

_______________________________________________
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.