[m-dev.] proposed command set for the internal trace based debugger

[Mireille Ducasse]

>> Being able to edit your source file, dynamically load it in,
>> and continue debugging the same run (using the "retry" or "redo"
>> command to re-execute the bit you just fixed) would be useful --
>> that allows you to quickly test a bug fix.  I have used that
>> feature in NU-Prolog and SICStus quite a bit.

Yes, indeed. Will this be possible ?


				- o -

By the way, Erwann has prepared a description of WHAT information can
be found in a trace. It explains what a goal path is and the different
ports.

The document is currently on my "to-be-proof-read" stack. As soone as
it is finished we will distribute it. That may help some discussions.