INI is great until you need to store anything with more than minimal structure. Lists and tables can be hacked in, but are not really supported.

I've had to write code like this: 

my $param = get_ini_param('Foo','Bar');
my @param1_params = split /,/, $param;

# repeat for 37 different parameters with different parsing requiremen
+ts, slightly different structure.

[download]
too many times. In the end I wind up rolling my own text serialization library just to use INI format.

YAML solves this problem very nicely and, IME, it is easy to edit by hand.


TGI says moo

In reply to Re^6: An Idiot's Guide to YAML by TGI
in thread An Idiot's Guide to YAML by scorpio17

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.