No, that's backwards. If you're building CGI, you do not want to use re eval. The default is the safety that I insisted they add.

Just use this: 

my $regex = param('foo');
$regex = eval { qr/$regex/ };
if ($@) { "it was bad... handle it" }

[download]
Then use $regex later, safely, as a compiled regex. In fact, wait, it's simpler than that: 
my $regex = param('foo');
$regex = eval { qr/$regex/ } or do {
  # handle failure
};

[download]
since eval will return undef on a failed block, or the compiled Regex object (always true) if it's a valid regex.

-- Randal L. Schwartz, Perl hacker

In reply to •Re: Re: ?Re: Re: Re: How to identify invalid reg. expr.? by merlyn
in thread How to identify invalid reg. expr.? by armyk

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.