I would say that it depends on how literally you take the word "always". e.g., If you've got a regex that is so simple as to need no explanation, I would say that including /x, but no internal whitespace/comments, is cargo cult because the /x has no effect. /m and /s are similarly pointless to include when dealing with data which is known to not contain newlines.
I'm always skeptical when I encounter the phrase "best practice". (In my experience, it tends to mean "We think this is the right thing to do, but can't be bothered (or aren't able) to explain why.") In this particular case, using /xsm with /(\d{3})-(\d{4})/ makes about as much sense as preferring $foo =~ /^bar$/xsm over $foo eq 'bar'. KISS. If you don't need the extra power/complexity, don't take special measures to make it available.
-
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.
|
