Update: I think Roy Johnson has it right -- watch out for the /g flag.

Something else is wrong:

>perl -demo Loading DB routines from perl5db.pl version 1.28 Editor support available. Enter h or `h h' for help, or `perldoc perldebug' for more help. main::(-e:1): mo DB<1> $sentence = 'sdfsdfsdf foo asdfklj bar ;alkdjdf' DB<2> x $sentence 0 'sdfsdfsdf foo asdfklj bar ;alkdjdf' DB<3> p "match" if $sentence =~ /foo/ && $sentence =~ /bar/ match
Either $sentence doesn't contain what you think it does, or you haven't run the code you posted. Or you need the /m flag. Or something else.

Please post the actual code (or better, a minimal example that behaves the same way), including the value of the variable involved in the match.

-QM
--
Quantum Mechanics: The dreams stuff is made of


In reply to Re: using && with regex in an if() statement by QM
in thread using && with regex in an if() statement by Tachoknight

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.