12 Feb
2005
12 Feb
'05
6:09 p.m.
How about this alternative. The profiler stores its own counter which defaults to 1. It implements an operator++ or a suitably named method (iterations? count?). then the on_* interfaces would receive a counted_sum object instead of just a duration_t. Basically, I'm looking for the ability to use a single instance of a profiler to collect stats for number of operations each of which are too brief to profile on their own, but when taken in aggregate you get meaningful data. Does this make sense? -- Caleb Epstein caleb dot epstein at gmail dot com