Parse::CSV would really fit the bill, I even demonstrated using a pipe sep over here.
But if you're stuck without using modules, you could probably rig sub up to do what you want easily. This just reads a text file of values in the form of:
some_key_param=value
my $config = read_config({ filename => 'some_config_file' });
# {{{ read_config
#
sub read_config {
my $args = shift;
die "No configuration file specified\n"
unless defined $args->{filename};
open my $conf_fh, '<', $args->{filename}
or die "Error opening conf file...$!\n\n";
my $conf = {};
for (<$conf_fh>) {
chomp;
# use '=' as the separator
if ( $_ =~ m/[=]/ ) {
# skip these lines
s/#.*//;
s/^\s+//;
s/\s+$//;
next unless length $_;
my ( $key, $value ) = split( /\s*=\s*/, $_, 2 );
$config->{$key} = $value;
}
}
close $conf_fh;
return $conf;
} # }}}
--
naChoZ
Therapy is expensive. Popping bubble wrap is cheap. You choose.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|