Re: Suggested improvement to the trace window

new topic     » goto parent     » topic index » view thread      » older message » newer message

Pete Lomax wrote:

> If you run the following code, you should see that it redisplays the
> entire screen more than it theoretically should have to, unless your
> PC is so fast you can't tell. You might want to check the line numbers
> are correct.
> 
> I have no idea whether there is an easy way to fix this, nor am I
> claiming it is important, but it distracted me enough from what I was
> doing to stop and write this(!). Obviously the blank lines are not
> blank in the actual code I am working on.
> 
> }}}
<eucode>
> with trace
> trace(1)
> 
> 
> procedure a()
> --line 6
> 
> 
> --line 13
> for i=1 to 100 do
> 	if i=95 then
> --line 16
> 
> 
> --line 23
> 	end if
> end for
> --line 26
> 
> 
> end procedure
> a()
> --line 34
> </eucode>
{{{


Good point, Pete, I think.
For now, try please (your code is condensed to show idea):

atom Z Z=0 procedure s() Z+=1 ? Z end procedure

with trace
trace(1)
s()procedure a()
s()--line 6
s()--line 13
s()for i=1 to 100 do
s() 	if i=95 then
s()--line 16
s()--line 23
s() 	end if
s()end for
s()--line 26
s()end procedure
s()a()
s()--line 34


You can set these s() with one push of F12 key or Ins key
in the ed editor, or add this command into your own editor.
When program is debugged, just delete these s() with the
Esc r command of ed editor.
Works for me just now, if I do understand your request correctly.

Regards,
Igor Kachan
kinz at peterlink.ru

new topic     » goto parent     » topic index » view thread      » older message » newer message

Search



Quick Links

User menu

Not signed in.

Misc Menu