| Warren Simmons 2004-06-28, 3:55 pm |
| Chuck,
How would you reply, if the specifications said, a. only when copy is
NOT used; or if it said, the source would be the same as the compiler
generated from; or if copy were made obsolete? Other methods might
be possible. And yes, current implementations would all probably have
to be impacted in some way. Yet, it seems the input to the compiler
in all cases has to include the resulting source code.
Warren Simmons
Oh, and what about the potential savings when the source is not
available, but the data file is? WS.
Chuck Stevens 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
>
>
|