Re: General Debugging Question

I have seen problems disappear once I have stopped using optimization (which
I usually do before debugging).  This is a rarity, and I am not sure why
things can sometimes go awry using optimization.

I actually _have_ seen what you are describing, when I have compiled without
saving in WDSc, or worse yet, saved half-way through making a change to a
program, compiled and witnessed outright silly behavior.  But this is
probably not the case.

On 1/16/06, steema@xxxxxxxxxxxxx <steema@xxxxxxxxxxxxx> wrote:
>
> ON more than one occassion I have noticed a problem in  a program, that
> will disappear after I have debugged the program. Is this rational, or
> there must be some other explanation?
> --
> This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list
> To post a message email: RPG400-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
> or email: RPG400-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/rpg400-l.
>
>


--
"Enter any 11-digit prime number to continue..."
"In Hebrew SQL, how do you use right() and left()?..." - Random Thought
"If all you have is a hammer, all your problems begin to look like nails"