One way to address this problem is to declare the config file variables as package-scoped in the main program (before reading the config file):
use vars qw($scalar1 @array2 %hash3);
Then they're available in all blocks
of the main program, including the external config file, without 'my' or 'local'. There can be significant drawbacks associated with global vars, but this approach works in Perl back to at least 5.04. Whereas 'our' was new in 5.6, I think.
You might find Dominus' Coping with Scoping to be a relevent read.
cheers,
Don
striving toward Perl Adept
(it's pronounced "why-bick")
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.