|Don't ask to ask, just ask|
Hm. Each of those warnings catch many of my most frequent typos and brain farts in first drafts of code.
However,I do agree with you that there are many situations where -- at least some of them -- are better ignored than coded around.
But, your "just disable them" code block makes it look more of a chore than is necessary:
(My point being that args to no warnings;can be multiple:no warnings qw[uninitialized numeric once void];
The one that really bugs me is:
But it is not the warning that bugs me, but rather the interpretation.
There is -- IMO -- absolutely no logic for allowing a space between a function name and its argument grouping parens. None whatsoever.
If the syntax required that if parens are used on a function call, the left paren must be abutted to the function name, that annoyance would go away.
I also wish that there were a :nocommon group label; though we could probably argue for a week about which should, and should not, be included :)
With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'
Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.