while( /foo(.*?)(tar)?bar/g ) { next unless $2; ... }

There might be a way to do something very tricky with zero-width assertions, but I find going the simple route is often much easier to maintain.

Updated the above to be simpler and added the following. The above returns "XfooY" for "fooXfooYtarbar" when just "Y" was wanted. So a simple state machine:

my( $state, $prev, @match )= ( "no foo" ); foreach my $tok ( split /(foo|tarbar|bar)/, $string ) { if( "foo" eq $tok ) { $state= "foo"; next; } elsif( "tarbar" eq $tok ) { if( "other" eq $state ) { push @match, $prev; # and/or do other stuff here } } elsif( "bar" ne $tok && "foo" eq $state ) { $prev= $tok; $state= "other"; next; } $state= "no foo"; }

        - tye (but my friends call me "Tye")

In reply to (tye)Re: repeating patterns 2 by tye
in thread repeating patterns 2 by iradik

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.