and simply moves on to the next element.

And that's the bug, IMHO. If the yes-pattern is present, and the condition fails, the whole match normally fails. Why should it move on if the match fails? Compare:

'a' =~ /^xa/ # match of x fails, doesn't move on to match a

When the no-pattern is not present, and the condition fails, it normally doesn't match:

$ perl -wE 'say "a" =~ /^(?(?=b)xxx)a/' $ # no match

So it doesn't show the "move on"-behavior when the yes-pattern is something else than the empty pattern.

So it's a special case. And it's not documented. So it's a bug.


In reply to Re^2: A bug in regex with conditional subpattern? by moritz
in thread A bug in regex with conditional subpattern? by Serge314

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.