[m-rev.] for review: implement undo for declarative debugger

[Ian MacLarty]

On 28 Jul 2005, at 14:51, Mark Brown wrote:

> On 28-Jul-2005, Ian MacLarty <maclarty at cs.mu.OZ.AU> wrote:
>> On Tue, 26 Jul 2005, Mark Brown wrote:
>>
>
> I suggest changing the whole description to:
>
> "Undo the effect of the most recent action that has not already been
> undone.  Actions that can be undone include giving the answers `yes',
> `no', `inadmissible', `trust' and `skip' and marking subterms.
>

That's not quite right either, since `undo' also undoes the effect of 
any other non-answer commands (like `set') that were executed after the 
answer that came before the most recent answer.  Also the second 
sentence might give the impression that you can undo specific answers, 
like "undo the last `yes' answer", which you can't do.

How about:

Reset the state of the declarative debugger to what it was before the 
most recent `yes', `no', `inadmissible', `trust', `skip' or `mark' 
answer that has not already been undone.

Ian.

--------------------------------------------------------------------------
mercury-reviews mailing list
post:  mercury-reviews at cs.mu.oz.au
administrative address: owner-mercury-reviews at cs.mu.oz.au
unsubscribe: Address: mercury-reviews-request at cs.mu.oz.au Message: unsubscribe
subscribe:   Address: mercury-reviews-request at cs.mu.oz.au Message: subscribe
--------------------------------------------------------------------------