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

[Zoltan Somogyi]

On 27-Sep-2000, Zoltan Somogyi <zs at cs.mu.OZ.AU> wrote:
> I think probably the best form is a single string option, called e.g.
> --suppress-events, which takes as its args a comma-separated list of
> event names or event class names to suppress. This could replace
> --no-trace-redo and --no-trace-internal, and I could implement it
> in a couple of hours.

I forgot to mention that the compiler would not pay attention to the value of
the --suppress-events option in declarative debugging grades, since the
declarative debugger's design requires all the events to be there.

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