1. trace window bug
Has anyone ever noticed or reported this before?
-- run this; press 'q'; press '?'; press 'i'; press ENTER
-- trace screen shows "i = 1000"
with trace
trace(1)
integer start
for i = 1 to 1000 do
end for
for i = 1 to 500 do
end for
for i = 1 to 10 do
if i = 5 then
trace(1)
start = i
exit
end if
end for
This should, at least, get a note in the docs. I'd rather have it
fixed but only if fixing it doesn't add any significant overhead.
Bob
2. Re: trace window bug
Bob Elia wrote:
> Has anyone ever noticed or reported this before?
>
> }}}
<eucode>
>
> -- run this; press 'q'; press '?'; press 'i'; press ENTER
> -- trace screen shows "i = 1000"
> with trace
> trace(1)
>
> integer start
>
> for i = 1 to 1000 do
>
> end for
>
> for i = 1 to 500 do
>
> end for
>
> for i = 1 to 10 do
> if i = 5 then
> trace(1)
> start = i
> exit
> end if
> end for
>
> <font color="#330033"></eucode>
{{{
</font>
>
> This should, at least, get a note in the docs. I'd rather have it
> fixed but only if fixing it doesn't add any significant overhead.
I'll fix it for the next release.
Loop variables at the top level are handled in a funny way.
They aren't really removed from the symbol table when
the loop ends, so the debugger displayed the wrong "i" in this
case.
Thanks,
Rob Craig
Rapid Deployment Software
http://www.RapidEuphoria.com
