Re: /Copy books - yes or no?

[Paul Raulerson <paul.raulerson@xxxxxxx>]

Good Lord, YES.  I don’t know anyone who opposes them actually.  

What are the reasons your friend has for not wanting to use copybooks? 

-Paul 

> On 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.