Here's some (untested) code:

my (@records, $cur_rec); while (<DATA>) { chomp; if (s/^\s+//) { $cur_rec->{'summary'} .= " $_"; next } my ($tick,$cust,$stat,$prio,$owner) = /^ ([\w-]+): \s* # ticket (\[.*?\]) \s* # customer (\[.*?\]) \s* # status (\[.*?\]) \s* # priority (\[.*?\]) # owner /x or next; $cur_rec = { 'ticket#' => $tick, 'customer' => $cust, 'status' => $stat, 'priority' => $prio, 'owner' => $owner, }; push @records, $cur_rec; }

You'll want to do better validation I expect. There are also ways to minimize the redundancy but that's left as an exercise for the reader :-)


In reply to Re: parsing multi-line output from a cli command by duff
in thread parsing multi-line output from a cli command by TASdvlper

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.