# NOTE: This looks a LOT scarier than it really is # "zzabbBBBBBBcdcdcdzz" =~ /ab*[cd]+/i rx_allocinfo P0, "zzabbBBBBBBcdcdcdzz" bsr RX_0 rx_info_successful P0, I0 rx_freeinfo P0 if I0, $match print "no " $match: print "match" end RX_0: rx_setprops P0, "i", 2 branch $start0 $advance: rx_advance P0, $fail $start0: rx_literal P0, "a", $advance $start1: rx_pushmark P0 $top1: rx_literal P0, "b", $start2 rx_pushindex P0 branch $top1 $back1: rx_popindex P0, $advance $start2: rx_literal P0, "cd", $back1 $top2: rx_oneof P0, "cd", $succeed branch $top2 $succeed: rx_succeed P0 ret $fail: rx_fail P0 ret

In reply to Parrot Regexes by BrentDax

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.