My advice is always to avoid global vars whenever possible. They are most always bad (say "I have 30 global variables, is that too many?" in the chatterbox and what happens). Machines are fast. Ram is cheap. I'd rather add a few clock cycles to the execution time than add a few hours to the debugging time.
As for a technique to apply... Instead of having 30 separate variables floating around, stuff similar groups of variables into either a module (as previously described) or use a hash. I describe the technique for using a hash here. Basically this is a best of both worlds scenario...to pass ALL your vars to your module you only have to copy 1 scalar if you us a hash ref (your coworker's big problem), you don't have tons of globals, and you don't have to remember the exact sequence of the 30+ vars you passed in.
HTH
/\/\averick
perl -l -e "eval pack('h*','072796e6470272f2c5f2c5166756279636b672');"
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.