|
The main advantage for having one function per service program is maintainability. It can get a bit messy if 2 developers try to modify different functions in the same service program. -----Original Message----- From: Schadd Gray [mailto:list@xxxxxxxxxxxxx] Sent: 15 October 2003 15:13 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. ------------------------------------------------------------------------------ The opinions expressed within this email represent those of the individual and not necessarily those of Gullivers Travel Associates (GTA). This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify postmaster@xxxxxxxxxxxxxxx Should you wish to use email as a form of communication, GTA are unable to guarantee the security of email content outside of our own computer systems. ________________________________________________________________________ This email has been scanned for all viruses by the MessageLabs Email Security System. For more information on a proactive email security service working around the clock, around the globe, visit http://www.messagelabs.com ________________________________________________________________________
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.