A simple profiler might be sufficient - it will tell you what was actually called, as opposed to what could possibly be called in any unrun branches of the code. Try Devel::DProf perhaps.
> I have a PDL script that relies on my private library of pdl > subroutines, but I don't want to send my complete library over to my > colleague. Instead, I want to find out all the subroutines called by > my script, and append them to the end of the original script. > > Does anyone know a way to run the script and find out all the > subroutines called as it runs? > > Thanks, > > Matt > > -- > Matthew Kenworthy / Assistant Astronomer / Steward Observatory > 933 N. Cherry Ave. / Tucson AZ 85721 / vox 520 626 6720 > > _______________________________________________ > Perldl mailing list > [email protected] > http://mailman.jach.hawaii.edu/mailman/listinfo/perldl _______________________________________________ Perldl mailing list [email protected] http://mailman.jach.hawaii.edu/mailman/listinfo/perldl
