The GUI now does realtime execution tracing. At present you have
to add commands like:
trace dummyid "dummy string";
to your program, then use the shell prompt:
bin/flx.py --force -DFLX_ENABLE_TRACE --test nbody 20
to set the -DFLX_ENABLE_TRACE macro on (hit RETURN not the
RUN button ..)
Each tracepoint will be shown in the window with an alternating
color. There is a one second delay at each trace.
There is also a silly bug in Tk with the yview method, which
adjusts the Text window to show the argument line (it puts the
line one off the top of the screen every time). I added 10,
but the it is still wrong: Tk should NOT move the display if
the line is visible.. so the text moves up and down as
different tracepoints are executed.
This mechanism can get more hairy later with selective
tracing, a speed control, profiling, coverage counts,
and other stuff. Also the Felix compiler can hopefully
be given a switch to instrument functions by adding in
a tracepoint at the start of every one (at present
you have to edit the code).
--
John Skaller <skaller at users dot sf dot net>
Felix, successor to C++: http://felix.sf.net
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Felix-language mailing list
Felix-language@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/felix-language
