- If you don't use strict, we won't want to help you.
- If you still don't use strict, we will NOT help you.
- It will catch mispelled variable names.
- It will catch missing '$', '@', '%', and '&'.
- It will force you to actually know what variables you're using.
- It will not let you use local unless you specifically say you want to. (Instead, you have to use our to scope globals.)
- It will prevent variable-clobbering due to scope changes. (You still shouldn't use the same variable name in different scopes, but this helps even if you're silly.)
- It will help you program better.
- It elevates Perl from the level of shell-scripting to the level of a true application.
- It makes maintenance of Perl applications possible. (I'm not exaggerating about this one.)
- And, the most important reason is "Because I said so."
We are the carpenters and bricklayers of the Information Age.
Don't go borrowing trouble. For programmers, this means Worry only about what you need to implement.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
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:
Outside of code tags, you may need to use entities for some characters:
- 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.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||