comment on

> ... e.g. the ability to include parenthesized sub-expressions in the "from" part and $1 back-references in the "to" part.

Honestly .... store the full real regexp in your config and eval it (or eval it into a sub to optimize execution time)

 
"245$a": [
        { "regexp": 's/(foo|bar)/He said "$1"/' }
      ]
[download]

There is no way to "safely" abstract the capture-var away, it has to be compiled into the regex and this needs an eval or /ee with all connected security issues.

> but bear in mind I do need the full power of regexp substitutions,

I have the impression your JSON format is an attempt to make it language agnostic. But the "full power" means you will be stuck with Perl.

And full power means that security becomes an illusion.


  DB<111> $_="abc"

  DB<112> s/(.)/@{[print "what? --> $1\n"]}/g
what? --> a
what? --> b
what? --> c

  DB<113>
[download]

Cheers Rolf
_{(addicted to the Perl Programming Language :)

Wikisyntax for the Monastery}

In reply to Re^3: Regexp substitution using variables by LanX
in thread Regexp substitution using variables by MikeTaylor

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Welcome to the Monastery
	PerlMonks