Re: Analyzing Perl Code

Replies are listed 'Best First'.
Re^2: Analyzing Perl Code by nitin1704 (Sexton) on Sep 18, 2012 at 16:59 UTC
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. :)	[reply]
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
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]