I have a hand-rolled template of key=value pairs that I'm parsing out of the body of an email, and checking each value for validity. One of these keys takes a URL as a value. Many mail readers will wrap long urls to the next line, so my original template, which looks like this...

<template>
  foo                = Yes
  bar                = 0
  blort              = 
  home_url           = http://www.foo.com/some/really/long/url 
</template>
[download]

...will end up looking like this, after I receive it in an email:

<template>
  foo                = Yes
  bar                = 0
  blort              = 
  home_url           =
http://www.foo.com/some/really/long/url 
</template>
[download]

What I'm trying to do, is "unwrap" that wrapped field before I process the template with Config::General to parse out the keys. Once the keys are properly unwrapped, Config::General has no problem with it. I also looked into Config::General's '-SplitDelimiter' option, but it doesn't consider a newline as whitespace, and my attempts at defining a proper delimeter there failed.

I've been working with a few monks on the CB (thanks diotalevi) to try to work this out, and we've come up with two possibilities, each with a flaw of their own. The problem is that some keys can be left blank, with no value, while others can have values.

This code below, one example of the unwrap code, which properly treats blank keys as it should, but doesn't unwrap the 'home_url' field back up to the previous line:

   use Data::Dumper;
   # This is actually in @body in the larger code
   open(TMPL, "<my.template") or die $!;

   my %template =
       map /(\S+)\s+=\s+(.*)/, split m((?<!\\)\n),
       ( do { local $/; readline *TMPL; }
         =~ m(<template>((?s:.*?)</template>)))[0];

   $Data::Dumper::Sortkeys = \%template;
   print Dumper(\%template);
[download]

This next bit of code actually unpwraps the 'home_url' field properly, but also unwraps keys with blank values into the value field of the previous key:

   use Data::Dumper;
   open(TMPL, "<my.template") or die $!;
   my $tmpl;
   for (<TMPL>) {
           next if /^#/;

           if (m!<template>!) {
                   $templ = "";
          } elsif (m!</template>!) {
                   my %hash = 
                      ($tmpl =~ /^s+(\w+)\s+=\s+(.*)$/mg);

                   if (%hash) {
                           $Data::Dumper::Sortkeys = \%hash;
                           print Dumper(\%hash);
                   } else {
                           print "Bad template: $tmpl\n";
                   }
           } elsif (defined $tmpl) {
                   s/^\s+/ /;
                   s/[ \t]$//;
                   s/=\s*\z/= /;
                   $tmpl .= $_;
           }
   }
   close TMPL;
[download]

This results in the output that looks like this:

$VAR1 = {
          'bar' => '0',
          'blort' => 'home_url  = http://www.foo.com/some/really/long/
+url',
          'foo' => 'Yes'
        };
[download]

Note how the 'home_url' key wraps up into the value side of the previous key.

What I'm trying to do, is keep all keys intact, including the 'home_url' one (which is the only key long enough to wrap, the others don't wrap).

Any helpful pointers here?

Update: I think jeffa is the winner on this one, the working code is now as follows:

   my $conf = new Config::General(
       -ConfigFile      => "pler.template",
       -ExtendedAccess  => 1,
       -InterPolateVars => 1,
       -AutoTrue        => 1,
       -StrictObjects   => 0,
   );

   my %config      = $conf->getall;
   my $template    = $conf->obj('template');
   my %params      = %{$config{'template'}};

   for (keys %{$config{template}}) {
           if (/^http/) {
                   $config{template}{home_url} = $_;
                   delete $config{template}{$_};
                   last;
           }
   }
   $Data::Dumper::Sortkeys = \%config;
   print Dumper(\%config);
[download]

---

---

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! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

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:
	&		&
	<		&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.