If you're so concerned about the complexity the config file, why don't you write an interactive configuration utility?

Back to the matter immedately at hand...

You keep talking about the config file, while you should be talking about the module that reads the config file and the program that uses the module. If you used the code I posted earlier in this thread, you could write your config file as:

[path]
root    = C:\test
code    = %root%\code1
include = %root%\include
lib     = %root%\lib

[download]

instead of

[path]
root    = C:\test
code    = C:\test\code1
include = C:\test\include
lib     = C:\test\lib

[download]

It doesn't get any simpler (from the config file's perspective). What else do you want?

In reply to Re^3: Config files by ikegami
in thread Config files by sparkel

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.