//'s not necessary if $regex was built with qr.

Actually, if you leave out the slashes, the regex is put in string context, and the speed gain is lost. 

$foo =~ '^string literal$';   # Does not equal /\Q^string literal$/
$foo =~ $string;
$foo =~ subroutine();
$foo =~ bareword;             # Unless $INC{'strict.pm'}
$foo =~ $precompiled_regex;   # Is stringified first!

$foo =~ /$precompiled_regex/; # Faster

[download]
I've even seen people do bizarre things because they think qr//s are faster without slashes: 
# Bad: (well, it works, but not the way you want it to)
$foo =~ $qr;
$foo =~ s//bar/;

# Good:
$foo =~ s/$qr/bar/;

[download]

- Yes, I reinvent wheels.
- Spam: Visit eurotraQ.

In reply to Re: Re: Set::Scalar - Regexp as method parameter? by Juerd
in thread Set::Scalar - Regexp as method parameter? by PetaMem

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.