Re: /Copy books - yes or no?

Hi Vern,

I've been away from RDi a long time now. I thought it was RD P for power.
I've been using RDZ. The copy members are only one click away and can be
opened by clicking on a variable instead of looking for the copy statement.
Glad to find something finally that works better in RDZ.

2015-03-12 14:08 GMT+01:00 Vernon Hamberg <vhamberg@xxxxxxxxxxxxxxx>:

The 2nd Con - looking at a separate source - in RDi it is as complicated
as a right-click on the /copy or /include name and click on a menu item.

Notice my smilie - :) and grin <vbg>

On 3/12/2015 7:50 AM, David Gibbs wrote:

On 3/11/2015 5:37 PM, Bob Cagle wrote:

Pro: Procedure prototypes don't have to be rekeyed everywhere

This is pretty much the ONLY thing I use them for ... and that enough is
worth any perceived hassle.

The risk of missing a prototype when you change the procedure interface
is far too high to risk not using a copybook. PLUS, modern change control
systems should track the use of copybooks and recompile programs that
reference them when changed (no vendor plugs here).

Con: Sometimes you need to see the code in the copy book, and

you have to go to a separate source to view it.

That is an absolutely trivial problem.

david

--
This is the RPG programming on the IBM i (AS/400 and 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.