David Foxwell wrote:
We do not have a single service program. Instead, we use an ordinary
module containing all the exported procedures. I understand that
means the code is duplicated by each program that uses the module. My
question is, so what? What are we missing.

The big issue here is ... when you change that module, you have to
recompile every program that includes that module. Keeping track of
that can be a bear (unless you have a good change management system <grin>).

If you use a service program, when you change the module, all you have
to do is rebuild the service program that the other programs reference
and everything will pick up the change.

Another problem is when we need to add a parameter to an exported
procedure. In RPGIII. How do we do this when the procedure is called
from a hundred others?

I'm not sure I understand the question ... if you add the parameter as
optional then the callers that don't have the parameter won't care.
Otherwise, you need to fix the programs that call that procedure.

david
(who works for a change management vendor in addition to running these
lists)




As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.