Re: /Copy books - yes or no?

[Alan Campin <alan0307d@xxxxxxxxx>]

All service programs have to have the prototypes published so you must use
them there.

I use standard copy blocks for standard constants, types, error models so
every program gets CB_STDTYPE and CB_STD_CON.

CB_API_HDR  RPGLE       Copy Block. API Standard Header.
CB_EXECCMD  RPGLE       Copy Block-Execute System Command.
CB_STD_CON  RPGLE       Standard Copy Block-Standard Constants.
CB_STD_EM   RPGLE       Standard Copy Block-Standard Error Model.
CB_STDTYPE  RPGLE       Standard Copy Block-Standard Types.

I, also, have standard copy blocks for display IO.

CB_KEYP     RPGLE       Standard Copy Block-Keys Pressed.
CB_MAP_IND  RPGLE       Standard Copy Block-Map Indicators to Fields.

I, also, use _LPR for local prototypes for multiple module programming.

So, yes I use them. Can't imagine doing ILE programming without them.

You could get by doing RPG III like monolith programming but don't see how
with ILE.

On Wed, Mar 11, 2015 at 4:37 PM, Bob Cagle <bcagle@xxxxxxxxxxx> wrote:

> Here's a fun topic:
>
> During lunch with my friend today I brought up the subject of copy books,
> and I was surprised by his complete and total vehemence against them.   His
> son was there also, who is currently learning C++, and he was surprised as
> well, since C++ makes frequent use of #Include statements.
>
> Personally, I have been using /Include in my RPG instead of /Copy, just
> because it looks more modern to me.
>
> So, do you use copy books in your RPG?  Why, why not?  Pros and Cons?
>
> I'll start:
>
> Pro:        Procedure prototypes don't have to be rekeyed everywhere
>
> Con:       Sometimes you need to see the code in the copy book, and you
> have to go to a separate source to view it.
>
> Thanks
>
> Bob Cagle
> IT Manager
> Lynk, Inc.
>
> --
> 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.