John D wrote:
"Walter Bright" <[email protected]> wrote in message
This goes back to my theory that a feature that encourages the programmer to insert misleading dead code to shut the compiler up is a misfeature.
A programmer who does the above is not a good programmer.


The reality is, even the best programmers will do such things if it is convenient to, even if they preach against it and know it is wrong.


That said, a compiler that doesn't warn that variables or arguments have gone unused in a function is not a good compiler. That said, a language that doesn't enforce return val checking is not a good programming language.

I often have unused variables and such when developing and debugging code, and when using conditional compilation, and having the compiler nag me about them would be very irritating.

Reply via email to