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

[Erwan Jahier]

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.

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

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

-- 
R1.


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