Re: [boost] Re: Re: Profiling Library suggestion

From: christopher diggins (cdiggins_at_[hidden])
Date: 2005-02-05 20:25:35

----- Original Message ----- 
From: "Philippe Mori" <philippe_mori_at_[hidden]>
To: <boost_at_[hidden]>
Sent: Saturday, February 05, 2005 7:01 PM
Subject: [boost] Re: Re: Profiling Library suggestion

> Well, profiling associated to a block covers most case but definitively 
> not
> all cases. So for other cases, we need to be able to start or stop the 
> profiler
> for a given counter.
>
> Cases where blocks profiling are not enough include :
>
> - Removing time elapsed in the user interface (say we display a message
> box to the user).
> - Profiling that should start in one function and end in another one.
> - We might need to stop accumulating before the end of the scope in some
> cases (for example, before displaying an error to the user).
> - Some timing might be related to event handling or idle processing.
> - We might want to deduce the time from an inner block to see the calling
> overhead.
>
> For most flexibility, we need automatic (RAII) and manual profiling
> (explicit start and stop and increment).

Good points. In your opinion would introducing:

 stop()
 continue()
 restart()

member functions be sufficient?

CD