Brian,
Isn't part of the goal (at least the optimize), to spend more time in compile to increase the performance of run time?
I don't think optimize was just to reduce the program size, but also the code efficiency.
-Craig
--- On Tue, 2/23/10, Brian Donaldson <[log in to unmask]> wrote:
From: Brian Donaldson <[log in to unmask]>
Subject: Re: Cobol Macros and $Control Options
To: [log in to unmask]
Date: Tuesday, February 23, 2010, 10:12 AM
In a message dated 2/23/2010 3:11:32 A.M. Pacific Standard Time,
[log in to unmask] writes:
I have a real 3 yorkshiremen (Python Monty) moment welling up here.
How many remember compile times in hours!
Dont pick on the MACROs they standardise code and reduce mistakes. The
better option is to break the code into separate source files
Actually, I had done that already -- $INCLUDE files.
My issue is that by removing all my safeguards (optimize=1, validate,
bounds, optfeatures etc) I am leaving myself wide open to disaster.
I'm not sure whether to keep them in or leave them out as the compile time
was seriously reduced
without these options.
Brian aka D.P. Gumby.
* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
|
