Re^5: Cleaning up unused subroutines

foo() may or may not be called, depending on @ARGV.

Better. A clear example rather than oblique allusions.

The only way to really do this was covered earlier: with a comprehensive test suite and gradual code modification.

And how do you test that your test suite is comprehensive?

Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.

"Science is about questioning the status quo. Questioning authority".

In the absence of evidence, opinion is indistinguishable from prejudice.

"Too many [] have been sedated by an oppressive environment of political correctness and risk aversion."

Comment on Re^5: Cleaning up unused subroutines

Replies are listed 'Best First'.
Re^6: Cleaning up unused subroutines by Somni (Friar) on Oct 26, 2007 at 13:03 UTC
And how do you test that your test suite is comprehensive? With code coverage checks, such as Devel::Cover.	[reply]
Re^7: Cleaning up unused subroutines by BrowserUk (Patriarch) on Oct 26, 2007 at 15:07 UTC
And how does Devel::Cover detect that unexecuted function call that you described back there somewhere? Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error. "Science is about questioning the status quo. Questioning authority". In the absence of evidence, opinion is indistinguishable from prejudice. "Too many [] have been sedated by an oppressive environment of political correctness and risk aversion."	[reply]
Re^8: Cleaning up unused subroutines by Somni (Friar) on Oct 26, 2007 at 15:19 UTC
Coverage checks are intended to determine how much of your code is exercised by your test suite. The basic presumption is that your test suite should call everything. If something is missed it's an indication that your test suite either needs more tests, or you have functions you aren't using. This differs from checking for unused functions by a chunk of code. A chunk of code, be it a script or a module, is not necessarily supposed to call every function possible on any given execution.	[reply]
Re^9: Cleaning up unused subroutines by BrowserUk (Patriarch) on Oct 26, 2007 at 15:43 UTC
Re^10: Cleaning up unused subroutines by Somni (Friar) on Oct 26, 2007 at 15:52 UTC
Some notes below your chosen depth have not been shown here
Re^6: Cleaning up unused subroutines by blazar (Canon) on Oct 27, 2007 at 12:23 UTC
And how do you test that your test suite is comprehensive? I personally believe that nothing will ever be 100% bulletproof, but modules like Devel::Cover and Test::TestCoverage should help.	[reply]
Re^7: Cleaning up unused subroutines by BrowserUk (Patriarch) on Oct 27, 2007 at 16:51 UTC
Did you read the rest of the thread? Bottom line:coverage tools don't help find unused subroutines. Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error. "Science is about questioning the status quo. Questioning authority". In the absence of evidence, opinion is indistinguishable from prejudice. "Too many [] have been sedated by an oppressive environment of political correctness and risk aversion."	[reply]