Seriously, everyone? More than 90% of config files are simple and can be processed in two lines of code (not counting formatting). Like this...open a file, and parse the lines with a map: 

    open( my $config_fh, '< :encoding(UTF-8)', '/some/path/.tofile' ) 
      or die "$0: Can't open config file. $!\n";

    my %creds = map { $_ =~ /(\S+)\s*?:\s*?(\S+)/ } <$config_fh>;

[download]

This will hande those simple key/value config lines:

    key: value

[download]

But at the end of the day, I would also say "standardize on a common CPAN module..."

In reply to Re^2: Config file by scott8035
in thread Config file by cajun

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.