The majority of the problems can indeed be solved that
way. (Though good luck if you forget a
local anywhere.)
But there are more subtle maintainability issues with
implicitly passing data in global variables. Code that
is explicit about where data that is being acted on came
from is better than code which hides that information
elsewhere.
This is also why I dislike local. Oh, I know when to use
it and I do use it correctly. But I prefer not needing it.
Perl has too many scoping mechanisms whose interactions are
too baroque. Rather few people really understand it, and
when people are working with interfaces they don't
understand they get confused and make mistakes. (Often
without knowing that they made mistakes.) As the
documentation says, local is probably not what you wanted
to use, my is generally more appropriate...
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:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, 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, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.