With static analysis, you'll probably not get very far, and it certainly won't be reliable.

Runtime analysis like what some profilers Devel::NYTProf and code coverage tools Devel::Cover do may work better, provided you've got enough "test" routines to cover all the code paths.

It's possible to build what you want with runtime inspections. Searching cpan for Devel might turn up something more directly suitable, but I'm not aware of anything that does exactly what you want. Sepia::Xref seems close, though.

"What should it profit a man, if he should win a flame war, yet lose his cool?"

In reply to Re: finding subroutine dependencies? by Joost
in thread finding subroutine dependencies? by Anonymous Monk

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.