I'm an advocate of
DRY, passing it around increases the error probability , e.g. typos.
OTOH globals tend to have a problem, if the line distance between creation and usage gets to big,
or generally if scope and context are not easy to oversee.
I'd use a block scope to simulate an object², the "global" is used like a class-attribute.
{
my $global="whatever";
sub method1 {
...;
foo($global);
...
}
sub method2 {
...;
bar($global);
...
}
sub ...
}
Closures are in most simple cases more elegant than objects, especially in perl¹!
(they just can't inherit, but that's not a "simple" case anymore).
UPDATES:
(¹) just compare to grandfathers lightweight object! No blessing, no $self ...
(²) "encapsulation" to be more precise
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.