If nothing else, just write something simple: 
my %ini;
my $group = "global";

while (<DATA>) {
   chomp;
   next if /^\s*;/ || !/\S/;   # skip comments/blank lines
   $group = lc($1), next if /^\s*\[([^\]]+)\]/;
   if (/^\s*(\w+)=/) {
      $ini{$group}->{lc($1)} = $';
   } else {
      warn "Parse error on line $.: $_\n";
   }
}

print $ini{global}->{this}, "\n";
print $ini{section}->{this}, "\n";

__DATA__

; sample data, this could be from
; a real .ini file for example..
; I hope I got the comment delimiter
; right.. maybe it's ' instead..

Some=sample data
this=this is an .ini file

[Section]
THIS=this will be in 'section' (note lower case) instead of 'global'

[download]

In reply to RE: RE: (4) Cross-platform config file parsing (hmmm... other hurdles?) by Fastolfe
in thread Cross-platform config file parsing by ybiC

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.