Further testing now yields the following code (Aristotle++ for the suggestion of using this module, and valdez++ for helping me figure out why the keys weren't captured properly)
     use strict;
     use Data::Dumper;
     use Config::General;

     my $conf = new Config::General(
                   -ConfigFile      => 'template.ini',
                   -ExtendedAccess  => 1,
                   -InterPolateVars => 1,
                   -AutoTrue        => 1,
     );

     my %config = $conf->getall;

     my $template = $conf->obj('template');

     my $backup_bit          = $template->backup_bit;
     my $beamable            = $template->copyprevention_bit;
     my $bpp                 = $template->bpp;
     my $maxdepth            = $template->maxdepth;
     my $url                 = $template->url;
     my $title               = $template->title;
     my $launchable_bit      = $template->launchable_bit;
     my $no_url_info         = $template->no_url_info;
     my $avantgo             = $template->AvantGo;
     my $compression         = $template->compression;

     print Dumper(%config);

     __END__

     <template> 
       url                =   
       AvantGo            = No
       maxdepth           =  
       bpp                = 4   
       compression        = zlib
       title              =  
       no_url_info        = 0
       copyprevention_bit = 0
       backup_bit         = 0
       launchable_bit     = 0
     </template>

[download]

Now let's see if it passes the litmus test of wrapping extremely long lines onto the next line. This template is in the body of an email message, limited by the wrapping capabilities of the MUA. I had this figured out in my original code as follows:

     my $line="";
     my @unwrappeddata;
     foreach (@body) {
             chomp $_;
             next if /^#/;
        
             if (m/^[^\s=]+\s+=\s*/ || m/^\[.*\]$/) {
                     $line =~ s/^#/\n#/m;  
                     $line .= "\n";
                     push @unwrappeddata, $line;
                     $line = $_;
             } else {
                     $line .= $_;
             }
     last if qw/</template>/; 
     }
     $line .= "\n";
     push @unwrappeddata, $line;

[download]

I'll keep marching along, this is working out well so far.

In reply to Re: Cleansing and stacking arguments before calling system() by hacker
in thread Cleansing and stacking arguments before calling system() by hacker

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.