| Joe Zitzelberger 2004-06-29, 3:55 am |
| In article <cbpgko$2ddj$1@si05.rsvl.unisys.com>,
"Chuck Stevens" <charles.stevens@unisys.com> wrote:
> "Joe Zitzelberger" <joe_zitzelberger@nospam.com> wrote in message
> news:joe_zitzelberger-1F0865.23493123062004@corp.supernews.com...
>
>
> None of the Unisys MCP compilers (any language) do so, and I'd contend that
> such a feature would present some problems in that environment, in which
> COPY is frequently used. Are the statements included via COPY to be
> included in the object code as well, or is the user expected to presume the
> presence of the library files after the main source has been reconstructed?
> If they're included, is it before or after any REPLACING statements have
> been applied? What about DMSII data bases? ADDS repositories?
>
>
> After some reflection, I feel obligated to quote my sainted mother: "A good
> idea, but not very much", at least for the environment with which I'm most
> familiar! ;-) Too many "gotchas".
>
> -Chuck Stevens
>
>
You get the actual source that was compiled -- after COPY processing.
The only exception is COPY SUPPRESS, which totally hoses the source
recovery.
|