On Thu, Jan 07, 2010 at 10:08:49AM +0000, Nicholas Clark wrote: > On Wed, Jan 06, 2010 at 10:07:32PM +0000, Tim Bunce wrote: > > > Actually, what I'd really like to see is the concept of a 'clock' > > abstracted further so there's a pointer to structure with pointers to > > functions and a some private data. Then the clock=X option would be much > > more useful. The usecputime and zero options would disappear and Nick's > > work on memory profiling could be folded in a a new kind of 'clock'. > > Any volunteers for that one? > > The thing I was thinking about memory profiling was that you could collect > that simultaneously with timings. So actually being able to collect 1 or more > "clock"s in a profile would seem to be the most useful system.
Yes, that would be a good next step after abstracting the "clock". > (No, I'm not volunteering right now) :) Me neither - apparently I'm supposed to be doing something with databases and perl 6... Tim.
-- You've received this message because you are subscribed to the Devel::NYTProf Development User group. Group hosted at: http://groups.google.com/group/develnytprof-dev Project hosted at: http://perl-devel-nytprof.googlecode.com CPAN distribution: http://search.cpan.org/dist/Devel-NYTProf To post, email: [email protected] To unsubscribe, email: [email protected]
