I guess read_config could look at the input file's layout and intuit whether you're separating section markers from config variables.

Maybe just adding a configurable parameter like 'noExtraNewlines' that would put newlines only in-between sections when adding entries ? That is, the current scheme of the user's file use of newlines would be preserved. Only new entries would be adopting the configurable option. Concern is, many users coudl eventually modify the same INI file, each one adding newlines when he/she sees it fit.

How about then an INI file formatter that would straigthen this out according to a defined (and configurable) scheme ? ;-)

In reply to Re^2: Config::Std blank entry in hash, and blank line by carcassonne
in thread Config::Std blank entry in hash, and blank line by carcassonne

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.