One school of thought is that warnings are there to help you during development of your application. They are there to warn (sic) you of things that are not fatal but might (and will if you let them) come back and bite you if you don't fix them.

The idea is then that once your development is done and your program does not generate any warnings any more, they are turned off in the released version. If your code is working according to specs (i.e. it does everything it advertises to do, and it does it in the way that is in the user documentation) and you have robust error handling in place, warnings are no longer necessary according to this school of thought.

The obvious flaws here are of course that: i) no application that is more complicated than Hello World is ever working to specs, ii) no one can foresee every error that can occur let alone test your error handling for it and iii) no application is ever bug free.

Consequently, for the very same reasons Abigail mentioned, I would prefer to leave warnings on. "It doesn't work" just is no fun as a bug report.

CU
Robartes-