While there's nothing wrong with your $LINE_PATTERN regex I think it would be simpler to keep the record and field/value processing separate. To my eye it looks tidier and easier to maintain but others may disagree.

use strict;
use warnings;

use Data::Dumper;

my $app_text =
   qq{one:partridge\ntwo:\nturtle doves\nthree:french hens\n};

my %fvPairs =
   map { split m{:\n?} }
   map { split m{(?<!:)\n} }
   $app_text;

print Data::Dumper->Dumpxs( [ \ %fvPairs], [ q{*fvPairs} ] );

[download]

produces ...

%fvPairs = (
             'three' => 'french hens',
             'one' => 'partridge',
             'two' => 'turtle doves'
           );

[download]

Cheers,

JohnGG

In reply to Re^2: Pattern match for split() - need match but not match syntax by johngg
in thread Pattern match for split() - need match but not match syntax by Tanoti

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.