This is a known bug in perl-5.6.1 - the regexp optimiser sees the initial ".*" and treats it as if it were anchored to the start of the string (which is fine), but fails to take into account the /g, which means that when the second match attempt sees that you are not at the start of the string it immediately aborts the match.

Small variations are enough to avoid the optimiser's error: anchoring the pattern with \G is one way:

  $testVar =~ /\G(.*?)\n\n/sg

[download]
and inserting an empty non-capture is another:
  $testVar =~ /(?:)(.*?)\n\n/sg

[download]

Hugo

In reply to Re: strange behaviour of /regexp/sg by hv
in thread strange behaviour of /regexp/sg by Jaap

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.