Re: /Copy books - yes or no?

I agree with the prevailing responses you've already received.

A small thing I'd like to add regarding C and C++: Their include files
are typically called "header files" or simply "headers". This makes it
very clear that they're meant for prototypes and other setup, not
arbitrary code.

I am going to guess that there is a decent-sized minority of RPG
programmers who "grew up" with pre-ILE versions of RPG. I'm not going
to say that these are categorically bad programmers. I think some
percentage of them are "modularity minded", making extensive use of
subroutines and using manageable, reusable *PLIST-called OPM programs.
Granted, not as nice as subprocedures and service programs, but still
a far cry from what I would call "monolithic".

Now, the point of that verbose preamble is this: I think THOSE
programmers are the ones who are most opposed to copy blocks. Because
really, what are you going to do with copy blocks in OPM? They don't
really gain you very much in OPM, and they still have all the
disadvantages.

Full disclosure: I consider myself a modularity-minded OPM RPG
programmer, and our codebase where I work is almost exclusively
"modularly OPM RPG IV". C was my primary programming language
throughout high school and college; I never heard of RPG or AS/400
until my first job after graduating.

John Y.