For Programmers: Free Programming Magazines  


Home > Archive > Cobol > August 2007 > COPY code in procedure division was Re: Stop Run vs GoBack









You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

 

Author COPY code in procedure division was Re: Stop Run vs GoBack
Clark F Morris

2007-08-19, 6:55 pm

On Tue, 26 Jun 2007 02:43:41 +1200, "Pete Dashwood"
<dashwood@removethis.enternet.co.nz> wrote:

>
>I also share your aversion to COPY code in the procedure division, and would
>never do this.
>
>(I don't even like doing it in the Data Division; instead I'd have an access
>module (for the file that would be COPYed) that combines procedure and data
>into a separate layer. Ths would then be CALLED instead of code being
>COPYed. I can generate such a module very quickly from templates I have.)


Actually if you copy code in as a nested program, you may get some
interesting optimization that separate linking can't provide. If
nothing else, the calling sequence may be optimized.

In terms of Data Division copies, I want them for all data
descriptions that are shared.
>
>Good job :-)
>
>Pete.
>

Sponsored Links







Also available: Server administration forum archive | Web Design forum archive | Software forum archive | Hardware reviews archive

Copyright 2008 codecomments.com