Thanks for the clarification and the pointers! I will have a look. Regarding building a parse tree with a recursive regexp, I found an inspiring example at ppp from demerphq (which seems a tiny bit hackish though). It uses a different technique with assertions that evaluate Perl code: 
use strict;
use warnings;
use Data::Dumper;

$^R=undef;
my $re = qr/
    (?{[$^R]})                      # initialize a new node in the par
+setree
                                    #   preserving the old as the 0th 
+element
    \(                              # match a paren
    (?>                             # atomic match
        ([^()]+)                    # capture
        (?{
            push @{$^R},$1;         # push the capture string into the
+ current node
            $^R                     # propagate the current node
        })
    |
        (?0)                        # recurse
        (?{
            push @{$^R->[0]},$^R;   # push the current node into the o
+ld node
            shift @{$^R}            # and restore the old node to be t
+he current
                                    # (while removing it from the new)
        })
    )*
    \)
/x;

"(a(b)(c(d)e)(f)g)" =~ m/$re/x
           and
print "matched\n"; 
print Dumper $^R;

[download]
which gives (with perl 5.10.0): 
matched
$VAR1 = [
          undef,
          'a',
          [
            'b'
          ],
          [
            'c',
            [
              'd'
            ],
            'e'
          ],
          [
            'f'
          ],
          'g'
        ];

[download]
But my current goal is not parsing, it is optimization of stringified output from parsed productions. It would have been cool to do optimizing transforms with recursive pattern substitutions. Then optimizations could be applied on the most nested level first, and propagate to higher levels.

In reply to Re^2: substitute with recursive regexps? by hexcoder
in thread substitute with recursive regexps? by hexcoder

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.