Beefy Boxes and Bandwidth Generously Provided by pair Networks
No such thing as a small change

Re: finding subroutine dependencies?

by Joost (Canon)
on Oct 01, 2009 at 21:52 UTC ( [id://798744] : note . print w/replies, xml ) Need Help??

in reply to finding subroutine dependencies?

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.

Replies are listed 'Best First'.
Re^2: finding subroutine dependencies?
by ELISHEVA (Prior) on Oct 02, 2009 at 07:10 UTC

    Covering all code paths is not necessarily possible. The range of possible value may be environment dependent and too large to test in any reasonable amount of time. Consider the following:

    sub makeUserSelectedObjectDance { # ENVIRONMENT DEPENDENT!!! # any class in @INC that has a dance method will be accepted my ($sClass) = @_; return if ! ($sClass->can('dance')); my $oDancer = $sClass->new(); $oDancer->dance(); return $oSomething; }

    or consider this routine which allows any valid combination of class and method. This kind of thing isn't all that uncommon when coding event-driven frameworks:

    sub applyUserSelectedActionToUserSelectedTarget { # ENVIRONMENT DEPENDENT!!! - relative to codebase size and contents # number of valid parings of class and method can be quite large # in a large codebase my ($sClass, $sMethod) = @_; my $crMethod = $sClass->can($sMethod); return if ! $crMethod; my $oSomething = $sClass->new(); $oSomething->$crMethod(); return $oSomething; }

    Best, beth

Re^2: finding subroutine dependencies?
by BioLion (Curate) on Oct 02, 2009 at 12:24 UTC

    Devel::NYTProf has worked wonders for me in similar situations - especially if you include the nytprofhtml program, which makes a browsable, annotated html document for all the code usage, including summary lists of all code called, how many times etc..., which will give you the dependancies you need.

    Although as Joost says this obviously depends on the tests being up to scratch!

    Just a something something...