Can I put in a vote for ~!? ;)

More seriously, one thing that's seriously missing is structured captures. With the addition of named captures, (?(DEFINE)...), and (more convenient) recursive patterns, the regex engine has all the necessary ingredients to implement fast recursive-descent parsers.

Well, all but one: there's no convenient way to get at the structure of the match to build up a parse tree. The raw materials to do so are there: you can take actions in code blocks and have them undone during backtracking via local; you can refer to capture groups by relative position and name so that embedded subpatterns work. But it's an enormous pain to put these ingredients together in any but the most trivial cases.

In reply to Re: What's missing in Perl 5.10 by educated_foo
in thread What's missing in Perl 5.10 by Jenda

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.