Sure, you want warnings turned on... for your own code. That's what use warnings is for.
Why would you want to use a global setting to cause other modules to throw warnings even though they are operating as intended? (as in the example)
| [reply]
[d/l] |
For one example, "-w" catches all kinds of data errors, from premature EOF to non-numbers where you expect numbers, when you pass a file handle to someone else's code. You'll get false positives, but you will also get a hint where the problem lies when you are getting unexpected results. Fix the ones you care about, remove the "-w" when you're done, and there you go. Monstrosities like "strictures", which turn on all warnings but only in your code, will not only miss these errors, but complain about non-problems.
| [reply] |
