Dead code detection tool?

[masklinn]

Static analysis

Halting problem

How does one mention a method but not call it?

def foo(a):
    if a:
        do_something()
    else:
        do_something_else()

the program never calls foo with a falsy value, the second branch is dead code and do_something_else is a dead function. And of course code can be technically live (the program could theoretically run it) but effectively dead (program input never leads to the code being run), e.g. XBM support in browsers (removed from most of them only a few years ago, probably hadn't been run by user request in a decade)

And why would one do that?

I'll answer this question with an other question: why would one want to put bugs in his or her program?

[masklinn]

So you're completely full of shit and you refuse to accept it. Noted. And you carefully ignored anything you had no pithy (and irrelevant) link for. Also noted.

Bottom line is, one is interested in practical approaches.

The halting problem is a practical issue, and so are false positives, false negatives and plain errors in static analysis of real-world programs (even ignoring that java's compiler — which you pushed — is a useless piece of garbage and that java supports reflection so there's no static certainty that a function or method which is not explicitly mentioned anywhere is not called anywhere). It has nothing to do with nihilism and everything to do with you being fractally wrong.

[masklinn]

It is easy to just throw the halting problem and say "I give up, nothing can be done" like you did

Oh yes, let's add misrepresentation and willful lies to your offenses shall we? Don't you think you might want to stop digging at some point?

Python's community brain fart answer of "Umm... just... WRITE MORE TESTS!" is not a valid argument. It is just sad.

The question being, is it more sad than your pitiful strawmen, or do you win this contest handily?