|
Ron, This is worth doing because "you never know." You might find that data area's are passé, and you want to switch to a control file. You might find a mis-spelt data area name someplace. You might find that you need to change the size/type of the data area. You might need to add some sort of error-recovery. You may have to add a default value or implement application-security. You just never know. Imagine having to make any of these changes in a dozen places in a hundred programs as opposed to one single spot. Make it a procedure and you have more options than inline code. More options = more maintainable. My apologies for the philosophical ranting. Buck Calabro Aptis; Albany, NY > -----Original Message----- > From: HwaRangRon@aol.com > Sent: Tuesday, November 16, 1999 12:22 PM > To: MIDRANGE-L@midrange.com > Subject: Procedures/Sub-Procedures > > We are starting the next release of our software, which is all in ILE RPG. > Now, I want to start taking common functions out of programs, change them > into sub-procedures accessed via a service program(s). Put the service > programs in a common binding directory and away we go.. > > One common function that all of our programs do is to get the current > company that they are working with by accessing a data area. It's only a > couple of lines of code, but I thought it made sense to put it into a > sub-procedure. However, I can not define a data area in a sub-procedure > (this also makes sense). > > So, I would have to create a full blown procedure (I assume not accessed > via a service program). So, my question is, Is this still worth doing - > given that it's only a couple of line of code retrieving a data area? > > Anybody have any comments? > > Ron > +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.