[m-dev.] Question about the current Mercury trace

[Mark Anthony BROWN]

Hi Erwan,

Erwan Jahier writes:
[Charset iso-8859-1 unsupported, filtering to ASCII...]
> Thoses questions are for Zoltan, Fergus, or Mark.
> 
> 1- Currently, no events are generated at the entry of the `if' branch of an
> if-then-else (at least with the version of mmc (3 months ago) I have). Why?
> Would it be difficult to add it?

You can get these events (as well as events at the entry and exit of
negations) by passing the '--trace-decl' option to mmc, in addition to the
'--trace deep' option.  The reason they are only generated with this
option is that they have only been used by the declarative debugger so
far.

However, I'd argue that they are more generally useful, so they should
be enabled by a separate option.  Or even better, they should be treated
like REDO events, which are generated by default but can be disabled
with the '--no-trace-redo' option.  So I propose we:

	- by default generate COND, NEGE, NEGS and NEGF events whenever
	  internal events are generated;
	- provide the options '--no-trace-cond' and '--no-trace-negation'
	  to disable these events.

Cheers,
Mark.

P.S. Note that '--trace-decl' has three dashes and no spaces.  Also, beware
that this is probably not a long term option, and is likely to be replaced
by '--trace decl' which will imply '--trace deep'.

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