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

[Fergus Henderson]

On 26-Sep-2000, Erwan Jahier <Erwan.Jahier at irisa.fr> wrote:
> Mark wrote:
> | 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;
> 
> I agree.

That sounds OK with me, but I would like to know how much it will cost
in terms of performance: how much bigger the debug grade executables
get, and how much compilation time increases by in debug grades.

> | 	- provide the options '--no-trace-cond' and '--no-trace-negation'
> | 	  to disable these events.
> 
> Ok.
> 
> But what about a finer grained way of disabling/enabling events by allowing to
> enable/disable them one by one? 

What would that be useful for?

> Is that tricky to implement? Or do you fear the extra number of options?

The latter.

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