Lesson: Warnings are there for a reason.
Yeah. Too bad some warnings are there because someone thought "I think this is bad coding style, let's issue a warning", and had their patch accepted. Luckely, most proposals like that never make it, but some did.
You shouldn't ignore a warning unless you have researched it and determined that you actually want to do whatever it is that's triggering the warning.
Yeah, but in most cases, it's bloody obvious.
THEN, you go ahead and document that this warning is expected and the reason why it's ok.
# Perl thought I thought that perl thought differently.
# Once again, perl was wrong.
# // Anonymous Monk, today.
no warnings 'some category';
AND THEN, you have another developer sign off on it.
Right. And next time, have him sign off when I want to blow my nose as well.
Both your names are in that comment forever and ever, amen!
Don't think so.
But you left out the important thing. You don't let the warning be issued, you turn it off using no warnings.