It's Because They Are Telling You Something About Your Code; It's Buggy!!!!
Worse than people of turning 'strict' are the people who don't understand 'strict' or 'warnings'. People who think that 'strict' or 'warnings' issueing warnings conclude the code is 'buggy' don't understand 'strict' or 'warnings'. And are hence not qualified to use it.
Yes, it's good to turn on strictness. It's good to turn on warnings. But it's only useful if you understand the messages it issues. Its messages indicate the code may have a problem spot. But it doesn't have to be, and perl may be wrong to. The conclusion that "oh, it gives messages under strict/warnings, hence the code is buggy" is too shortsighted, and a signal of poor understanding of Perl.
Note that I'm not claiming the code you refer to doesn't have bugs - it probably has. I'm just ranting about your generalisation.
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.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||