== Quote from John D (jd...@googling.com)'s article > A programmer who does the above is not a good programmer. 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.
Think about it for a minute. When is the last time you checked the return value for printf() in C? Would you really want the compiler nagging you about something like this?
