I am writing an application to modify ini files on existing embedded architectures.

Each platform is configured using a variety of ini files in various different locations.

The application needs to preserve comments in the file since they contain (among other things) CVS information.

My problem is that there are a large number of ini/config handling modules on CPAN Config::IniFiles, AppConfig, Config::IniHash, Config::Tiny, Config::Simple, Config::Backend, etc.

As such, I am looking for recommendations from anyone who has used some of these modules and has a preference for one over the other.

I don't have any control over this architecture so solutions such as YAML or XML aren't an option.

Thanks.

In reply to Recommendations for an INI handling module by Anonymous Monk

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.