Re: /Copy books - yes or no?

[Bradley Stone <bvstone@xxxxxxxxx>]

I use them with great enthusiasm.

Have't run into an issue with them unless you're sloppy and keep different
"versions" of them in your library list.  But that's user error.

I actually try to keep them in QCOPYSRC so if I need to view it, I know it
has the same name (or same with a different prefix) than the module
source.  Easy to get to and see.

Brad
www.bvstools.com

On Wed, Mar 11, 2015 at 5: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.