Timer library

[Alex Kiernan]

Russ Allbery <rra at stanford.edu> writes:

> Fabien Tassin <fta at sofaraway.org> writes:
> > According to Alex Kiernan:
> 
> >> OK, that makes sense. I've given the library code the first n elements
> >> (depending on what's in the enum) so that things like history routines
> >> in the libary can be timed, you then start your application numbering
> >> at n+1 and pass N to the TMRinit routine. Per-application strings get
> >> passed into summarise & it has the library strings hard coded.
> 
> > it is possible to use nested timers ?
> > It is the reason I've created the history timer... it is sometimes
> > interesting to have reports of nested functions as a tree like the one
> > I've shown as a sample of "stathist".
> 
> The current innd timer code will do nested timers, or at least I didn't
> see any reason why it couldn't the last time I looked it over.  It was
> just that innreport didn't understand how to summarize the output in a way
> that made sense.
> 

Doh - why didn't I realise that! (Too busy thinking about how you'd
thread it, at least thats my excuse...)

-- 
Alex Kiernan, Principal Engineer, Development, Thus PLC