A brute force way might be to remove any of you
personal libraries from the @INC and run the
program and see what barfs...

--Chris

Matthew Kenworthy wrote:
> 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

_______________________________________________
Perldl mailing list
[email protected]
http://mailman.jach.hawaii.edu/mailman/listinfo/perldl

Reply via email to