Re: /Copy books - yes or no? -- RPG400-L

Subject: Re: /Copy books - yes or no?
From: Buck Calabro <kc2hiz@xxxxxxxxx>
Date: Thu, 12 Mar 2015 10:07:53 -0400
List-archive: <http://archive.midrange.com/rpg400-l/>
List-help: <mailto:rpg400-l-request@midrange.com?subject=help>
List-id: "RPG programming on the IBM i \(AS/400 and iSeries\)" <rpg400-l.midrange.com>
List-post: <mailto:rpg400-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/rpg400-l>, <mailto:rpg400-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/options/rpg400-l>, <mailto:rpg400-l-request@midrange.com?subject=unsubscribe>

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.

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.