You wrote:
> what conditions must be in place in order to turn a
> complete program into a 'magic box' or function that
> can be included in another program?
You need to be more careful of scoping issues, particularly
if you're using lexical variables. For exmaple, if you
declared your hash as a file-scoped lexical (
my) variable
in your code, it wouldn't be available to the script
that
require-d it.
Another issue is that the script you're require-ing has
to return a true value; that's why such scripts often end
with
1;
You might also want to put the code that reads the config
file into a subroutine that you can call. And you might
want to read
perlmod.
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.