Re: Analyzing Perl Code

[toolic]

in reply to Analyzing Perl Code

Since your blog mentions tracing several times, CPAN has handy modules, such as Devel::Trace and Devel::DumpTrace.

It might be worth copy and pasting key excerpts from your blog here (in readmore tags) in case your link becomes stale.

[nitin1704]

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. :)

[davido]

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.

[Jenda]

Devel::TraceSubs then.

[nitin1704]

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?