I have a system where a user provides a set of regular expressions and a set of replacement strings (what you put in the right side of the s/// operator). All of these 'rules' (not to be confused with Perl 6 rules) can be embedded inside each other. The problem with embedding is that it can make managing numeric capture groups references difficult to deal with. If you embed one rule in another and they both have capture groups, the numbering of capturing groups gets shifted in the final combined regex gets shifted around. I'd like to be able to not require the users to think about this problem which means that part of my preprocessing code that runs before actually creating the final regex needs to some how figure out where all the capture groups are and renumber the references and back references appropriately. This seems to be not an easy problem, but I'm hoping that there might either be a simple solution other than parsing the whole regex myself or a good regex parser around that I could use to manage this problem. Does anyone here know of good tools for finding out where all the capture groups are inside a regular expression?

--DrWhy

"If God had meant for us to think for ourselves he would have given us brains. Oh, wait..."


In reply to Is there an easy way to parse and modify regular expressions programmatically by DrWhy

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.