Regarding not wanting to write your own parser, it's actually not that bad. I have a little one that I've been using for small config files for awhile; nothing fancy but it works: 

sub readConfigFile($){
    my $cfgfile = shift;
    my %cfg;
    open(CONFIG, $cfgfile) or die " Error opening $cfgfile: $!\n";
    while (<CONFIG>) {
        next if /^\s*$/;
        next if /^\#/;
        chomp;
        next unless /=/;
        my ($key, $variable) = split(/=/,$_,2);
        $variable =~ s/(\$(\w+))/$cfg{$2}/g;
        $cfg{$key} = $variable;
    }
    return %cfg;
}

[download]

In my opinion, this is a nifty and simple little config file parser.

In reply to Re: Using do to read config by mull
in thread Using do to read config by BazB

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • 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:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.