[m-rev.] diff: debugger todo list

[Simon Taylor]

On 10-Jan-2003, Zoltan Somogyi <zs at cs.mu.OZ.AU> wrote:
> On 10-Jan-2003, Simon Taylor <stayl at cs.mu.OZ.AU> wrote:
> > +<li> trace builtins and semidet unifications
> 
> Implementing this would not be difficult, but it would increase the overhead
> of debugging hugely; it could double both the time and the code size overheads.
> Given that builtins and unifications cannot have implementation errors inside
> them, this is too high a price.

They can't have implementation errors inside them, but they can fail
when you don't expect them to.  At the moment it can be difficult to
debug cases where a complicated if-then-else condition fails unexpectedly
because you aren't given any information about which goal failed.
Tracing of unifications and builtins could be enabled on a per-module
basis.

Simon.
--------------------------------------------------------------------------
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
--------------------------------------------------------------------------