Re: /Copy books - yes or no?

Yes, for things like constants and prototypes.

Never did like them for executable code, though. IMHO, way to much chance of undesirable side effects and way to many dependencies needed in the using code. Callable programs or procedures should be used instead.

Sam

On 3/11/2015 5:37 PM, Bob Cagle 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 email has been checked for viruses by Avast antivirus software.
http://www.avast.com