[m-dev.] logging proposal

[Mark Brown]

On 18-Mar-2006, Ian MacLarty <maclarty at cs.mu.OZ.AU> wrote:
> On 3/18/06, Julien Fischer <juliensf at cs.mu.oz.au> wrote:
> > What I was getting at here, is that `debug' may not be a general enough name
> > because you may want to generate logging traces for purposes other than
> > debugging.
> >
> 
> What about 'trace' goals?

I think `trace' is exactly the right name.  Particularly if the behaviour
is determined by the trace level (possibly a new trace level) and the
presence of the `--trace-optimized' option.

> 
> > > 2.  Should debug goals be allowed to be enabled in non debugging grades?
> > >     If not then you couldn't use debug goals to profile your app in hlc
> > >     grade for example.
> >
> > I would argue that they should (particularly in light of the fact that
> > the debugger doesn't work in the hlc grades).
> >

Is that really a problem?  To what extent are you expecting this feature
to replace the functionality of mdb and/or the profilers?

> 
> I think I agree, though Mark's concerns are still valid.  Are there
> any other opinions on this?

I guess I'd be happy with it being turned on at a new trace level that
sits in between `none' and `shallow', and this trace level needn't require
a low level C grade.

Cheers,
Mark.

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