First: It is really not recomended to use regex to parse htlm (tends to turn into a nightmare).

Second: You need to use the s modifier on your regex in order to make . match the newline character.

Third: using .+ is greedy, and will match from the first <!-- Start_of_revision--> to the last <!-- End_of_revision--> (which I am sure is not what you want).

Forth: The code below is untested

@revision_array=();
my $start = qr/<!-- Start_of_revision-->/;
my $end   = qr/<!-- Start_of_revision-->/;
if (m/$start((?:(?!$end).)+)$end/msg)
    {
    push (@revision_array, $1);
    }

[download]

Update: And to get all of them, that if should be a while

They say that time changes things, but you actually have to change them yourself.

—Andy Warhol

In reply to Re: pattern matching by JediWizard
in thread pattern matching 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.