Because these scripts reach-out and touch production files/databases, a solution that requires running the script is not a happy one.
The ultimate goal would be a "lint" type of check for each perl script that can be run when the script is submitted for production release. There is also the problem of having .. 5 different Linux servers without identical perl modules installed. My boss that wants the ability to know if a script working on machine A can be moved to machine C. This means identifying the real required modules and perhaps documenting them, but not trusting the "use" statements at the top of each script.
I hoped I could comment out all "use xxxx" statements and run "perl -c" or "perl -Mdiagnostics" and get a list of all the un-resolved function calls. This would at least get me started.
But.. un-resolved function calls generate run-time errors. (grrr). Any thoughts?
In reply to Thank you for the thoughts
by FatDog
in thread How do I detect what modules are not being used?
by FatDog
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |