From: christopher diggins (cdiggins_at_[hidden])
Date: 2005-02-04 19:33:59
----- Original Message -----
From: "Pavel Vozenilek" <pavel_vozenilek_at_[hidden]>
>> Any comments or suggestions?
> Useful would be to have:
> - ability to report data only when certain threshold is reached
Threshold of what?
> - collecting min/max/average statistics where needed
This could be done relatively easily, I believe by writing a new policy.
Would you be interested in writing a statistics collecting policy?
One thing that concerns me is that as far as statistics go, this will likely
have far too coarsely grained resolution to be used, as one would a real
profiler. Due to the resolution of the underlying boost::timer. This is
instead useful only for large and extremely CPU intensive blocks of code.
Perhaps "profile" is a bad name, and instead it should be called
"progress_timer", because it is little more than a high-powered version of
the original progress_timer.
Object Oriented Template Library (OOTL)
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk