I'm using primary module for config variables etc.. like this..
package SA::Config;
use strict;
BEGIN {
require Exporter;
@SA::Config::ISA = qw(Exporter);
@SA::Config::EXPORT = qw(%c);
}
our %c = (
var1 => '/blah',
logDir => '/var/log'
);
1;
then in your scripts :
use SA::Config qw(%c);
This way i.e when storing as HASH u don't clutter
the namespace and config variable usage is easy spotted..
Faster way can be also to place all your virables in file
and then "require" them, but this has some disadvantages..
(One more thing i do is separate utilities functions into
separate Utils.pm module..).
Other thing that comes to my mind :") along these lines is
to use different name spaces f.e. :
Project1::Config
Project2::Config
... etc..
this way u can have common lib directory for all your projects w/o having problem between them..
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, 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, 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.