You can make your own class to process config files.
For plain config files it may looks like this:
package PlainConfig;
use strict;
use Carp;
use vars qw($AUTOLOAD);
sub new{
my $self=shift;
my $config=shift || croak "There is no path parameter specified";
my $new={};
open CONFIG, $config || croak "Couldn't open config file - $config";
while (<CONFIG>){
s/^\s*//;
next if (/^\s*#/ or /^$/);
/^([^=\s]+)\s*=\s*([^\n\r]*)/;
$new->{$1}=$2;
}
close CONFIG;
bless $new, $self;
return $new;
}
sub AUTOLOAD{
my $self=shift;
my $attr=$AUTOLOAD;
$attr=~s/(.*::)+//;
return $self->{$attr};
}
1;
Then your script will be looks like this:
use PlainConfig;
my $config=new PlainConfig;
print "Username: ".$config->username."\n";
But there are many other approaches. Choose the best.
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.