|
So far Roy no one has discussed performance; only technique and style. What are the facts on what happens in the various scenarios? Is there a difference in the compiled application if one has included dozens of unused modules vs. spending the time and energy to be sure only those modules needed are included? Coding styles and standards are important of course but what worries me is that the idea of black boxing solutions for everyday problems seems to be a casualty in this discussion. It would seem to me that the end game is to provide a simple and well documented means for a shop to provide tested and error-free solutions to everyday programming problems. It seems obvious from the amount of interest, the variety of opinions, and the length of this discussion that the Service Program algorithm is neither simple nor clear. Here is an instance where we really don't care about efficiency in my opinion, we only care about effectiveness. Effectiveness includes such things as ease of documentation, ease of training, ease of use, ability to find existing code and reuse it, and the ease of passing on knowledge to new staff members as they come on board. (my terminology is no doubt wrong however please look past that to the issue I am trying to get a handle on.) --------------------------------------------------------- Booth Martin http://www.MartinVT.com Booth@xxxxxxxxxxxx --------------------------------------------------------- -------Original Message------- From: RPG programming on the AS400 / iSeries Date: Thursday, October 16, 2003 11:25:12 AM To: RPG programming on the AS400 / iSeries Subject: RE: Function Opinion Yes, let's debate this one intelligently. I am trying to compromise between some people on my shop on this one. Most of those who object, performance wise, against a big service program and/or a big /COPY of all the prototypes for the service program are those who wouldn't use a service program not written by them regardless. Rob Berendt -- "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." Benjamin Franklin
As an Amazon Associate we earn from qualifying purchases.
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.