if the user is perlwise (and only then), my favourite option is to simply put the config-data as perl code in the config-file, like 
"root"          => "/path/to/root",
"filepath"      => "/path/to/files",
"ftp_instances" =>
[
    {
        "sourcepath" => "/source/path/on/server",
        "savepath"   => "/save/files/here",
    },
    {
        "sourcepath" => "/source/path/on/server",
        "savepath"   => "/save/files/here",
    },
]

[download]
Then you can simply read the file, do 
eval "%CFG = (" . readfile("cfg") . ");";

[download]
and you´re gone.

The benefit is that you can safely bring in all kind of difficult data (newlines etc.), and you can use an idiom you are pretty much used to.

just my $ 2/100

In reply to Re: Configuration file design by holli
in thread Configuration file design by castaway

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.