The quotes seem to be fine at my end...at least, warnings doesn't indicate any special issue with them. Warnings just says there's an unrecognized escape in the line where I escaped the period and indicated a space with \s. As far as my eye can see, there should be no error there.
Line under discussion:
$query = "(St\.\s)(Mt\.\s)(?=Helens)";
Unrecognized escape \s passed through at blah... line x

Perl is saying that it figures you made a mistake with \s. It translated that into a single "s" character. It also translated \. into a literal single character of '.' but it knew about escaping a period and Perl didn't complain about that.
Consider the following:

#FROM INCOMING FORM INPUTS
$query = '(St\.\s)(Mt\.\s)(?=Helens)';  #right way
print "$query\n"; ##(St\.\s)(Mt\.\s)(?=Helens)

$query = "(St\.\s)(Mt\.\s)(?=Helens)";  #your way
print "",$query,"\n"; ##(St.s)(Mt.s)(?=Helens)
print "$query\n";     ## same thing (St.s)(Mt.s)(?=Helens)

$query = "(St\\.\\s)(Mt\\.\\s)(?=Helens)"; #ok, but confusing
print "$query\n";    ## (St\.\s)(Mt\.\s)(?=Helens)

[download]
Fixing the quoting has real consequences in terms of what $query winds up being!
I always "use warnings;". I very rarely ignore a warning, with the possible exception of working with old code and the "deprecated syntax" warning. However, in all cases I do strive to understand what the heck is wrong that Perl is complaining about and then try to "make Perl happy". Sometimes with deprecated syntax, the error may be so pervasive that is not practical.

I understand that in your production code, this string will come from elsewhere instead of an assignment statement like above. Be that as it may, I still strongly advise understanding what a Perl warning is telling you and fixing all test code so that it runs without any warnings. I have heard that Perl runs slightly slower with warnings enabled. I have never benchmarked that because this just hasn't been a significant factor in my work. I recommend leaving warnings enabled at all times.

In reply to Re^3: Evaluating user-entered captured groups during Perl substitution by Marshall
in thread [SOLVED] Evaluating user-entered captured groups during Perl substitution by Polyglot

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.