comment on

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

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Think about Loose Coupling
	PerlMonks