The greediness is just your first problem.

Problem #2: You're using the g modifier in list context, causing all the matches to be returned at once. You'll never print anything other than the first file name. 

pos $data = 0;
my $len = length $data;
while (pos $data < $len) {
   if ( $data =~ m{ \G ( .+?  \. xml ) }gcxms ) {
      print "$1\n";
   }
}

[download]

Problem #3: If there's anything after the last .xml, you have yourself an infinite loop. Checking if pos is less then length is a bad idea when using the c modifier. Fix: 

pos $data = 0;
for (;;) {
   $data =~ m{ \G ( .+?  \. xml ) }gcxms
      or last;

   print "$1\n";
}

[download]

Finally: Using the c modifier is rather useless, ugly if you only have one regexp, and it's rather complex (as shown by the number of errors). Fix: 

while ( $data =~ m{ \G ( .+?  \. xml ) }gxms ) {
   print "$1\n";
}

[download]

Tip: If you really did have a use for c (e.g. if you were writting a lexer), then you'd have multiple regexps, and aliasing $_ to the variable containing the text would be worthwhile. 

for ($data) {
   pos() = 0

   for (;;) {
      /\G ... /xgc && do { ...; next };
      /\G ... /xgc && do { ...; next };
      /\G ... /xgc && do { ...; next };
      last;
}

[download]

In reply to Re: non-greedy piecewise matching by ikegami
in thread non-greedy piecewise matching by mifflin

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.