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:
C:\test>perl -M-warnings=uninitialized,numeric,once,void -E"123;$x=1;p
+rint $y; 'A'+0"
C:\test>perl -Mwarnings=uninitialized,numeric,once,void -E"123;$x=1;pr
+int $y; 'A'+0"
Useless use of a constant in void context at -e line 1.
Useless use of addition (+) in void context at -e line 1.
Name "main::y" used only once: possible typo at -e line 1.
Name "main::x" used only once: possible typo at -e line 1.
Use of uninitialized value $y in print at -e line 1.
Argument "A" isn't numeric in addition (+) at -e line 1.
(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:
C:\test>perl -wE"say (1+2)*3"
say (...) interpreted as function at -e line 1.
Useless use of multiplication (*) in void context at -e line 1.
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.
RIP Neil Armstrong
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] |