Re^2: Analyzing Perl Code

in reply to Re: Analyzing Perl Code
in thread Analyzing Perl Code

Thanks toolic! These modules seem to be great and much easier to use, though, they produce really detailed traces (one line for every statement). I would like just one line for each subroutine entered, because the scripts I'm working with are really long. Nevertheless, I will try these modules and see how it works out. :)

Comment on Re^2: Analyzing Perl Code

Replies are listed 'Best First'.
Re^3: Analyzing Perl Code by Jenda (Abbot) on Sep 19, 2012 at 00:06 UTC
Devel::TraceSubs then. Jenda Enoch was right! Enjoy the last years of Rome.	[reply]
Re^4: Analyzing Perl Code by nitin1704 (Sexton) on Sep 19, 2012 at 14:48 UTC
Thanks Jan, I noticed that your module uses Hook::LexWrap too. So I was moving in the right direction after all. Today I found this other module Debug::Trace. I have a feeling TraceSubs is probably better with it's indented output representing call depth. Debug::Trace on the other hand doesn't require any changes in the source code. Are there any other differences?	[reply]
Re^5: Analyzing Perl Code by Jenda (Abbot) on Sep 19, 2012 at 21:45 UTC
I've never used Debug::Trace and it's ages since I used Debug::TraceSubs for the last time so I can't comment. To minimize the changes to the code you can put all the Devel::TraceSubs related code into a separate file and add just `require 'that_file.pl';` into the source, under the use statements. It's not perfect, but the $devel_tracesubs->trace() needs to run after all the subroutines you want to track were loaded and defined. Jenda Enoch was right! Enjoy the last years of Rome.	[reply] [d/l]
Re^3: Analyzing Perl Code by davido (Cardinal) on Sep 18, 2012 at 17:43 UTC
Though Perl is not officially an acronym,there are various backronyms in usage, such as: Practical Extraction and Reporting Language. If the trace dumps are too long, find a common feature that you are interested in, and filter everything else out. Dave	[reply]

In Section Meditations