...it's likely better not to use anything that exotic in production code.

You're absolutely right, and I probably should've added a "still experimental" warning. (In fact, I wouldn't use it myself, if my well-being depended on it :)  OTOH, if people never really use those more exotic features (and report bugs, if found!), they'll remain experimental forever...

As to the original problem, does anyone know if backrefs are supposed to work within the {} quantifier, or not? (In the docs, I couldn't find anything explicit either way.)  I can well imagine that it's non-trivial to implement, but as the OP said, it doesn't seem too far off to attempt to use them that way, in particular as they do work outside of the quantifier.


In reply to Re^2: Backref in a regex quantifier by almut
in thread Backref in a regex quantifier by Anonymous Monk

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.