Obviously, m/MI-6/x (they want to match "MI-6", not "m/MI-6/x"). How could that be corrected for?

Most of programming is asking yourself how you know something. The code to teach the machine to know it falls out from that.

So, how would you know whether they entered a piece of Perl code instead of a regex? If you decide arbitrarily that it's when something begins "m slash", then there's your solution: use a regex to extract the piece. Maybe they select another form element that says "I'm entering a regex instead of a piece of Perl code", or something. But an arbitrary string is neither a regex nor a piece of Perl code (maybe they wanted to match something that begins with m slash).

Of course, the simplest way to correct for it is with humanware instead of DWIM-ware. Put a big message by the input box that says "enter a regex, not a piece of Perl code!". Sometimes, the simplest solutions are the best.

-- Randal L. Schwartz, Perl hacker

And, of course, you can compile the regex that they entered using qr//. You should run that in an eval and if it fails then you know that they've entered and invalid regex and you can go back and ask for a better one.

--
<http://www.dave.org.uk>

European Perl Conference - Sept 22/24 2000, ICA, London
<http://www.yapc.org/Europe/>

And when they wonder why /5/ doesn't match 5?

perl -e '$in = "/5/"; $m = qr/$in/; print 1 if 5 =~ $m'
[download]

BlaisePascal actual hit it on the head. I'm not sure what drugs I was on Saturday to so blindly accept what you said. What I've really got is input from RecDescent parsed language. One of the things that I accept in my language is a "perl pattern match". For conveniece sake, I want to permit the user to specify whatever delimeters they want. Then, one or more patterns are joined to together, and I let perl regex engine do the hard work. I think tilly's suggestion of qr// is probably the right call. I can apply that "early on", and know that the escaping in the RE has been properly applied.