On Wed, 14 Nov 2001, Darrin Thompson wrote:

> Is it appropriate to just be reported in the same way as process time 
> and controlled by a switch? You could just substitute in the different 
> measurement method (wallclock time) into your current implementation. 
> Then all the reporting mechanisms could be reused. The idea is to help 
> identify bottlenecks that are IO related, i.e. database programs. So a 
> high degree of accuracy isn't all that important and a line profiler is 
> probably most useful.
> 
Yes, that sounds kind of useful. I'll put it on the todo and we'll see
when there's time to do it.

On a related note, I wonder if anyone got ideas for how to give command
line options to a program specified with "-r" such as in

ruby -r rbprof myscript.rb --timer=wallclock -o calc.results

and I want --timer option to go to rbprof and all other to the
"real" script. Ok, I could simply have rbprof take away its options and
give them silly, long names that are unlikely to be for the "real" scripts
but are there better solutions?

/Robert