[m-rev.] for review: programatically turn profiling on and off

[Peter Ross]

On Tue, Sep 26, 2006 at 03:46:58PM +1000, Julien Fischer wrote:
> 
> On Tue, 26 Sep 2006, Ian MacLarty wrote:
> 
> >On Mon, Sep 25, 2006 at 09:05:03PM +0200, Peter Ross wrote:
> >>Hi,
> >>
> >>Provided no-one sees problems with this change.  The next plan is
> >>to add a library module which allows one to turn profiling on and
> >>off as impure predicates.
> >>
> >
> >I don't think they need to be impure, since they can go inside trace
> >goals (and therefore have access to the IO state).
> >
> >What about adding the new preds to the benchmarking module instead of
> >adding a new module?
> >
> 
> I don't think that the benchmarking module is the appropriate module
> to add this to.  I would rather have a new module, e.g. runtime_util,
> or some thing that included the predicates to turn profiling on or off
> and the predicate to write out trace counts etc.
> 
I will add them in the new module, runtime_util unless there are any
other objections.
--------------------------------------------------------------------------
mercury-reviews mailing list
Post messages to:       mercury-reviews at csse.unimelb.edu.au
Administrative Queries: owner-mercury-reviews at csse.unimelb.edu.au
Subscriptions:          mercury-reviews-request at csse.unimelb.edu.au
--------------------------------------------------------------------------