From: Dermot <paik...@googlemail.com> > I have been asked to look at/add features to an existing ModPerl app > that has thousands of lines of code spread over tens of modules. Some > are OO, some are function-oriented. There looks like there's lots of > debris and unused functions. For clarity, simplicity and > maintainability, I want to remove the stuff that is no longer used or > needed. Is there any module/method that can help me trace what > functions are being used? I could add a print statement to every > function but that would take a while to do and then I'd have to parse > the http logs to correlate the data. What I think I need is some > independent module that sits at the top of the name-space and logs the > functions to a separate log. Does anyone have any ideas that might > help? > Thanx, > Dp.
Looks to me like you are looking for a profiler. Have a loop at CPAN - http://search.cpan.org/ Jenda ===== je...@krynicky.cz === http://Jenda.Krynicky.cz ===== When it comes to wine, women and song, wizards are allowed to get drunk and croon as much as they like. -- Terry Pratchett in Sourcery -- To unsubscribe, e-mail: beginners-unsubscr...@perl.org For additional commands, e-mail: beginners-h...@perl.org http://learn.perl.org/
