In general, you probably don't want to pull out the m or s modifiers unless you are going to attempt to make a match across lines. Wisdom, if there were such, would follow the principle of parsimony. Solve simple problems simply, and save the bells and whistles for harder problems.

My advice would be to process any multiline string in which you are only seeking to match within individual lines as an array of lines to match against individually. You've run afoul here of exactly the kind of problem that you should not even need to hanker with.

There is a reason why the newline character is such an important part of the regexp world. Don't go there, unless you have to. And when you do, you'll learn certain practices that become more important when matching across lines. Until, then solve your simple problems simply and move on.

Explaining to you the finer points of regexp design is not even appropriate at this point, as the principle of parsimony has precedence.

---

---

• Are you posting in the right place? Check out Where do I post X? to know for sure.
• Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:

  <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>

• Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
• Want more info? How to link or How to display code and escape characters are good places to start.