[m-rev.] for review: improve the declarative debugger user interface

[Ralph Becket]

Ian MacLarty, Monday,  2 May 2005:
> On Mon, 2 May 2005, Julien Fischer wrote:
> > > +
> > > +Because pure Mercury code does not have any side effects, the declarative
> > > +debugger can make inferences such as ``if a call produces incorrect output
> > > +from correct input, then there must be a bug in the code executed by one of
> > > +the descendents of the call''.
> > > +
> > I suggest adding something like:
> >
> > 	i.e the code called during the call.
> >
> 
> I think that will sound a bit clumsy.  Are you worried users will be confused
> by ``descendents of the call''?  I could change it to ``if a call produces
> incorrect output from correct input, then there must be a bug in the code
> executed during the call'' if you like.

I think your original wording is fine.

-- Ralph
--------------------------------------------------------------------------
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
--------------------------------------------------------------------------