That's an excellent point actually. I'll amend my answer, although I covered it somewhat. Assuming you actually trust the user, this seems like a sane way to do it. 
my $regexp = <$file_handle>;
my $creg   = eval { qr($regexp) };

if( $@ ) {
   warn "regex error: $@";

} else {
   if( $something =~ $creg ) {
      # do wonderful things.
   }
}

[download]

I apparently skipped the meat of the question because it seemed clear to me that the reason the matching failed was because of an interpolation problem with a test regexp that he generated between quotes and he wasn't actually reading it from the user -- which would have likely worked the way he had it.

-Paul

In reply to Re^3: Comparing two variables when one variable includes a regexp... by jettero
in thread Comparing two variables when one variable includes a regexp... by fiddler42

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.