[m-rev.] for review: making the decl debugger "smarter"

[Fergus Henderson]

On 06-Sep-2002, Mark Brown <dougl at cs.mu.OZ.AU> wrote:
> Make the declarative debugger more flexible with how it interprets
> trace event sequences.  This makes the declarative debugger "smarter":
> it is now able to handle code that makes use of solutions/2 and its
> variants, and it is not confused if it misses some events due to shallow
> tracing.

That looks fine.

> The requirements on trace event sequences are:
> 
> 	1) if there are any events from a certain class (e.g. interface events,
> 	   negation events, disj events) then we require all events of that
> 	   class;
> 
> 	2) if there are any disj events, we require all negation events
> 	   and if-then-else events.

This statement should be incorporated in the comments in the source code.

-- 
Fergus Henderson <fjh at cs.mu.oz.au>  |  "I have always known that the pursuit
The University of Melbourne         |  of excellence is a lethal habit"
WWW: <http://www.cs.mu.oz.au/~fjh>  |     -- the last words of T. S. Garp.
--------------------------------------------------------------------------
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
--------------------------------------------------------------------------