morgon: Further to Corion's post:
[Corion]: The match runs to completion before the map even starts.
At the time your map runs, $1 and $2 are what they are at the end of the global match.
Here's an instrumented version of the OPed code to better (I hope) show what's happening:
c:\@Work\Perl\monks>perl -wMstrict -le
"use Data::Dumper;
;;
my $s = \"1 A\n2 B\n33 foo\n\";
;;
my %h =
map { print qq{in map: \$_ '$_' \$1 '$1' \$2 '$2'}; $1 => $2; }
$s =~ /(\d+)\s+(\S+)/mg
;
print Dumper(\%h);
"
in map: $_ '1' $1 '33' $2 'foo'
in map: $_ 'A' $1 '33' $2 'foo'
in map: $_ '2' $1 '33' $2 'foo'
in map: $_ 'B' $1 '33' $2 'foo'
in map: $_ '33' $1 '33' $2 'foo'
in map: $_ 'foo' $1 '33' $2 'foo'
$VAR1 = {
'33' => 'foo'
};
(Note that this example doesn't take into account the revised data format specification suggested here. :)
Give a man a fish: <%-{-{-{-<
-
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.
|