[m-dev.] for review: new ports for the declarative debugger

[Fergus Henderson]

On 14-Sep-1999, Zoltan Somogyi <zs at cs.mu.OZ.AU> wrote:
> 
> > Should these ports should be documented in the debugging chapter of the
> > Mercury user's guide?  I think they probably should, since if the user
> > compilers with --decl-debug, then they will see those ports.
> 
> I will, later; this is meant to be a minimum change to allow Mark to
> work on a fix for a problem we found while writing the declarative debugger
> paper.

Fine.  (Incidentally, I also need to document the "exception" port...)

> The larger question is whether the compiler should generate these events
> even if --trace-decl is not specified, and the larger still question is
> whether there should be a --trace-decl option at all. I think that when the
> declarative debugger is working properly, which it isn't at the moment,
> then every executable compiled with deep tracing and internal events
> should enable declarative debugging. This means generating the new events
> and reserving the stack slots declarative debugging needs. At the moment,
> it needs two, but there is no particular reason why it can't make do with one.

That sounds good to me.

-- 
Fergus Henderson <fjh at cs.mu.oz.au>  |  "I have always known that the pursuit
WWW: <http://www.cs.mu.oz.au/~fjh>  |  of excellence is a lethal habit"
PGP: finger fjh at 128.250.37.3        |     -- the last words of T. S. Garp.
--------------------------------------------------------------------------
mercury-developers mailing list
Post messages to:       mercury-developers at cs.mu.oz.au
Administrative Queries: owner-mercury-developers at cs.mu.oz.au
Subscriptions:          mercury-developers-request at cs.mu.oz.au
--------------------------------------------------------------------------