Re: Perfrom Thru
From: Chuck Stevens (charles.stevens_at_unisys.com)
Date: 03/23/04
- Next message: Howard Brazee: "Re: Perfrom Thru"
- Previous message: Chuck Stevens: "Re: Perfrom Thru"
- In reply to: Chuck Stevens: "Re: Perfrom Thru"
- Next in thread: Joe Zitzelberger: "Re: Perfrom Thru"
- Reply: Joe Zitzelberger: "Re: Perfrom Thru"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Tue, 23 Mar 2004 10:05:00 -0800
I wrote:
<Either you give the user control over whether (carefully-written
user-optimized or not) code (carefully-written user-optimized or not) is
indeed efficient -- by giving the user control over whether a "silent"
inter-segment transfer is permitted to occur. >
More clearly:
Either you give the user control over whether (carefully-written
user-optimized or not) code is indeed efficient -- by giving the user the
ability to prohibit a "silent" inter-segment transfer is permitted to occur
inside that piece of code -- or you don't. Unisys MCP/AS COBOL74, if it
errs in this regard, errs on the side of giving the user greater control
over the efficiency of his program at the expense of the possibility that if
the user fails to exercize that option appropriately the result *can* (under
very limited circumstances) be an uncompilable program.
-Chuck Stevens
- Next message: Howard Brazee: "Re: Perfrom Thru"
- Previous message: Chuck Stevens: "Re: Perfrom Thru"
- In reply to: Chuck Stevens: "Re: Perfrom Thru"
- Next in thread: Joe Zitzelberger: "Re: Perfrom Thru"
- Reply: Joe Zitzelberger: "Re: Perfrom Thru"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]