×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
On 3/11/2015 6:37 PM, Bob Cagle wrote:
So, do you use copy books in your RPG? Why, why not? Pros and Cons?
Yes, pervasively.
Pro: Procedure prototypes don't have to be rekeyed everywhere
Along with any other typical 'definition-only' code like a standard
H-specification. I keep all this stuff in QPROTOSRC (tip o' the hat to
David Morris for the idea) because that lets me keep the same member name:
QPROTOSRC ACCTSRCV - A/R prototypes
QRPGLESRC ACCTSRCV - A/R procedures
ACCTSRCV *SRVPGM - A/R procedures ready for consumption
Con: Sometimes you need to see the code in the copy book, and you have to go to a separate source to view it.
This is one of SEU's pain points that goes away with RDi. When I was an
SEU-er, I used compiler listings extensively.
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.
midrange.com
