You say ... the application is large and escape is a terrible job.
Well, how many separate source code files are there that make up the application? How many of them yield that sort error message when you run perl -Tcw on each file? Among the affected files, how many lines of code actually cause that error message?
The error messages are "machine-readable" -- they report the line numbers and the affected strings in a consistent way. If it turns out that there are hundreds of lines to fix, you'll probably notice that they fall into a smaller number of patterns, and you can write a perl script to read the error messages and update the affected lines of the affected files -- saving the updated code in a separate directory, of course, so that you can run diff on the pre- and post-edited versions to confirm that all and only the intended changes have been made. (If there are just a few dozen lines to fix, stop complaining and just fix them.)
In reply to Re: Unescaped left brace in regex is passed through in regex
by graff
in thread Unescaped left brace in regex is passed through in regex
by gzh
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |