Greediness is often misunderstood, but actually that is beside the point considering the regex supplied. After all, what are you saying when you say s/\s+|\n/ /g? Consider...
$data = "\n\n\n";
$data =~ s/\s+/foobar/g;
This outputs "foobar", because \n is whitespace covered by \s.
Both * and + are greedy operators when not flipped to non-greedy by the application of ?. True, the implications of greediness are very important when greedy operators are combined with alternation (as above), but those implications do not come into play given the example.
In the given regex, if you used ? to change your greedy + operator to non-greedy, then the RHS of the alternation operation would be applied. Regardless, the effect would be the same (' ' would be substituted for \n versus for \s, but you'd see the same result). Update: Let me strike that last bit. Got effect of ? on alternation messed up. Rest of explanation is fine (I think).
Forgive me if I am missing something (I have the feeling I must be).
On another note (to the original author of the SOPW node), please note that you don't need multi-line matching here. The m and s regex modifiers only have to do with "^", "$", and ".", not with \s.
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>
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
Want more info? How to link
or How to display code and escape characters
are good places to start.