If you are creating a module to include configuration information, you might find the following useful. Firstly, we create the module that holds the configuration information, making sure the proper things are exported. Source:
package Testing;
use strict;
use Exporter;
our @ISA = qw(Exporter);
our (%EXPORT_TAGS);
$EXPORT_TAGS{'config'} = [qw($verbose $debug)];
Exporter::export_ok_tags('config');
our ($verbose, $debug) = (1,1);
1;
And the main script that exploits the configuration information:
use strict;
use warnings;
use Testing qw(:config);
print "I am ", $verbose ? "" : "not ", "verbose\n";
print "I should ", $debug ? "" : "not ", "debug\n";
When the code directly above is run, it produces, as expected:
I am verbose
I should debug
For instance, if we changed this line (
our ($verbose, $debug) = (1,1); ) in the configuration module, to (
our ($verbose, $debug) = (undef,undef); ) we would get:
I am not verbose
I should not debug
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.