>>41
So, basically, if you totally ignore compiler warnings, but write a shitload of tests and have your code widely used for a long time, and THEN start to fix those warnings, two things happens: first, you find that most of the bugs resulting from the suspicios code were already discovered by your users and the aforementioned shitload of tests, second, by rewriting the code, especially unexperienced as you are with the compiler's complaints, you occasionally introduce new bugs. No shit, Sherlock! Yet the conclusion is a non-sequitur, isn't it?