From perlop:
The /g modifier specifies global pattern matching--that is, matching a
+s many times as possible within the string. How it behaves depends on
+ the context. In list context, it returns a list of the substrings ma
+tched by any capturing parentheses in the regular expression. If ther
+e are no parentheses, it returns a list of all the matched strings, a
+s if there were parentheses around the whole pattern.
The reason your first regex worked as planned was because there were no capturing parentheses. Thus only what matched was returned.
In the second regex, you have two sets of capturing parens. If you look at the pattern of undefs in @b, you can see it's returning undef when the other half of the regex doesn't match.
I'm not exactly sure how you could match that the way you want using one regex alone and still retain the matching capabilities.
-
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.
|