Re: A Text_IO fixes it?

["C Bass" <cmbass@mindspring.com>]

You are probably right. Unfortunately, it is hard to minimize what all it
fixed in the 120k+ lines of code we have for this program. It may have been
the optimization for the GUI code (that seemed to be causing the problems).

The *real* problem is that I am about to leave this job for another and
no-one else there has the knowledge to do what I had intended to do
(re-write the GUI). We have one package that creates all the widgets used,
but that one file is 20,000+ lines long. This is really unnecessary as most
of the code can be written into reusable procedures. But as I said, I am
leaving (soon) and don't have the time to rewrite it. :(

Canada

"Robert A Duff" <bobduff@world.std.com> wrote in message
news:wcc7li6de0f.fsf@world.std.com...
> "C Bass" <cmbass@mindspring.com> writes:
>
> > You were right, it was the compiler. I had no set the optimization level
and
> > it was using the default ptimization level for the compiler. I turned
off
> > optimization and everything seemed to be working just fine. It actually
> > fixed quite a many error we have found.
>
> If turning off optimization changes the program's behavior, that does
> not *necessarily* mean there's an optimizer bug, as you seem to imply.
> It could also be that your program does something erroneous
> (unpredictable), and it happened to do some damage when optimized, but
> it happened to work when not optimized.
>
> If you have a small test case, it might be interesting to see it...
>
> - Bob