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