In someways you should first consider how much code you need to examine and your timeframe. Do you spend 5 days goofing with the computer when if you simply printed and read the code, taking notes, would provide the overview you need. And it only took 2 days.

Look at cpan with keywords like, profile, debug, dbug, trace, etc. *grep'ing is problematic in that method calls are on objects, but you need to know what the object is to be able to know which method is meant.

Moose provides meta info on classes etc. Code needs to be written using it...

Debug::Trace has a unique approach.

There have been various attempts at providing a filter for Doxygen.

In reply to Re: how can I get here? by otto
in thread how can I get here? by perl5ever

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.