[m-rev.] for review: document the decl debugger

[Fergus Henderson]

On 25-Aug-2002, Zoltan Somogyi <zs at cs.mu.OZ.AU> wrote:
> On 23-Aug-2002, Mark Brown <dougl at cs.mu.OZ.AU> wrote:
> > @@ -1609,10 +1612,28 @@
> >  @item deep
> >  A procedure compiled with trace level @samp{deep}
> >  will always generate all the events requested by the user.
> > -By default, this is all possible events,
> > +By default, this is all the usual events,
> >  but you can tell the compiler that
> >  you are not interested in some kinds of events
> >  via compiler options (see below).
> 
> We should consider generating all events even with --trace deep by default.

I think that is a good idea.  How much extra code space / compilation time
will it cost?

> Don't mention two- versus three-value debugging; most readers won't know
> what you mean. Just say what the current implementation does; you can update
> the documentation when you implement three-valued debugging.
...
> Likewise, don't mention the display of contours until we can display them.

But do put "@c XXX ..." comments in the TexInfo source, so that
we don't forget about these issues.

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