RE: [boost] Re: Re: Re: Re: Latest version of the profiler

From: Brian Braatz (brianb_at_[hidden])
Date: 2005-02-11 11:25:02

> -----Original Message-----
> From: boost-bounces_at_[hidden] [mailto:boost-bounces_at_[hidden]]
> On Behalf Of Sérgio Vale e Pace
> 
> On Thu, 10 Feb 2005 17:33:19 -0700, Brian Braatz <brianb_at_[hidden]> wrote:
> > Yes- those are the words I was trying to say.
> >
> > I might want to accumulate ALL of the calls, in one big honking list. Or
> > I might want a "overview" of the average of each profile point.
> >
> > I think we need both, in addition to allowing me to put metadata into
> > the profile point. Because with the metadata, I can now go back through
> > the accumulated list and filter out what I care about.
> >
> > ** this is the big piece that is missing for me from off the shelf
> > profilers **
> 
> smells like mixins to me. something like this would be apropriate (pseudo
> code)?
> {
>   profiler< log_all< log_overview<> > > prof;
>   // profiled code
> }
> 
> Sérgio
[Brian Braatz] 
Hmm.. I think so. As long as there were enough methods available to me in the right fashion to allow the weave above to be able to do that. That answer would require more study.

Part of the issue though, is I cannot put the metadata in, so the log_overview<> implementation might be convoluted since it is trying to double track things.

Please see my next mail suggesting multi-index- I THINK that would speak to the issues I am talking about and it would give the users enough power to be able to use the profiler in MANY different ways.