AW: Function Opinion

Well, may be it's caused by the fact, that they had before ILE already the
expression "Service Program", which were quite normal sub-programs for
exactly the same functions than we do now with procedures in service
programs. Such namings and their dependent usage "glues" in programmer
heads.

Werner Noll

-----Ursprüngliche Nachricht-----
Von: Booth Martin [mailto:Booth@xxxxxxxxxxxx]
Gesendet: Mittwoch, 15. Oktober 2003 16:53
An: rpg400-l@xxxxxxxxxxxx
Betreff: Re: Function Opinion


A feature of collecting similar functions into broadly grouped service
programs is that programmers will learn where and how to find available
functions in a fraction of the time. 
 
One thing I am beginning to see with the one function per service program
policy is that duplicates are popping up under different names simply
because the number of service programs in a shop is becoming overwhelming.
 
(this is an opinion, of course. I am looking forward to reading the
responses of others)
---------------------------------------------------------
Booth Martin http://www.MartinVT.com
Booth@xxxxxxxxxxxx
---------------------------------------------------------
 
-------Original Message-------
 
From: RPG programming on the AS400 / iSeries
Date: Wednesday, October 15, 2003 9:22:27 AM
To: RPG programming on the AS400 / iSeries
Subject: Function Opinion
 
I have a client that insists on creating service programs with only one
function per service program. I have always been of the opinion that all 
like" functions should be contained in a service program together.
 
That being said, are there any benefits or possible issues with having only
one function per service program?
 
Thank you,
Schadd Gray
Damon Technologies, Inc.

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