This might get you started:

#! /usr/bin/perl use strict ; use warnings ; $|++ ; my $data = qq{ [...] <body> [...random stuff...] <li>headline one</li> <br> <p>the story</p> [...random stuff...] <li>headline two</li> <br> <p>the next story</p> [...random stuff...] <body> } ; while ( $data =~ s{<li>(.*?)</li>.*?<p>(.*?)</p>}{}s ) { print "Headline: $1\nStory: $2\n\n" ; } __END__

That is, of course, assuming that the only use for <li> and <p> are only used for headlines and stories. IMO, the more restrictive you can make this regexp, the better.

Update: This is probably better done with a proper parser. I've never used it, but HTML::Parser might be a good option.


_______________
D a m n D i r t y A p e
Home Node | Email

In reply to Re: Multiple Multiline Regexps? by DamnDirtyApe
in thread Multiple Multiline Regexps? by Anonymous Monk

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.