foo() may or may not be called, depending on @ARGV. This is just a very simple example of the larger problem: subroutines may or may not be called based on conditions that can only be determined at run-time.
The only way to really do this was covered earlier: with a comprehensive test suite and gradual code modification.
In reply to Re^4: Cleaning up unused subroutines
by Somni
in thread Cleaning up unused subroutines
by koknat
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |