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

[Mireille Ducasse]

>> In fact we have a better scheme in mind (based on *all* I/O actions
>> generating a log record, and being able to roll the log forward/backward
>> at will), but that requires a significant amount of extra work. 

Both parts of the sentence sound reasonable !

				- o -

>> Being able to compile code (a query, a condition on a break point)
>> at debug time is also something that we will address later, but not now.
>> However, *replacing* part of the code of the running program is not something
>> that I envisage the trace based debugger will *ever* do, because it requires
>> working at the object code level, which is something we have avoided
>> assidiously since the start of the project. 

I agree.

				- o -

All the discussion about HOW to abstract the list of ancestors means
one thing to me : the primitive should give the plain list, and the
abstraction mechanismS should be left to Opium.