Re: hash and array mismatch

You are using the same key for multiple values. You will only retain the last value assigned to the hash for a given key. For example 'TOTAL QUALITY' has values 8 and 14, only 14 is retained.

Most likely a hash is not appropriate for whatever you are trying to achieve. You could however:

use warnings;
use strict;
use Data::Dump::Streamer;

my @data = <DATA>;
my %dataPos;

chomp @data;
push @{$dataPos{$data[$_]}}, $_ for 0 .. $#data;

Dump (\%dataPos);


__DATA__
WELL
TOTAL QUALITY
POSITION NAME

TOTAL QUALITY
POSITION NAME
[download]

Prints:

$HASH1 = {
           ""        => [ 3 ],
           "POSITION NAME"
                     => [
                          2,
                          5
                        ],
           "TOTAL QUALITY"
                     => [
                          1,
                          4
                        ],
           WELL      => [ 0 ]
         };
[download]

Which creates a list of positions for each key value.

DWIM is Perl's answer to Gödel

Comment on Re: hash and array mismatch Select or Download Code

Replies are listed 'Best First'.
Re^2: hash and array mismatch by TGI (Parson) on May 10, 2007 at 17:06 UTC
Very interesting! At first glance your code didn't look right. So I read more carefully and saw what was bothering me: `push @{$dataPos{$data[$_]}}, $_ for 0 .. $#data;` [download] You are pushing data onto an undefined value that is dereferenced as an array! The script should (I thought) die the first time through the for loop. But it works. So I did some experimentats and read the docs. I found out that you can do this: `my $foo; # $foo is undefined push @$foo, 23; print "I found @{$foo}\n";` [download] Further testing showed that: `push @{ undef() }, 99;` [download] Died as I had expected. Further tests show that unshift works the same way. Also, pop and shift will create array references. `my $foo = undef; shift @{$foo}; print "Foo: $foo\n"; # prints Foo: ARRAY(0x12121212)` [download] The various docs don't mention this special behavior. Thanks for the education. TGI says moo	[reply] [d/l] [select]
Re^3: hash and array mismatch by GrandFather (Saint) on May 10, 2007 at 19:19 UTC
It is called "autovivification". Have a read through perlreftut and perlref. You have seen it happen in a light weight way whenever you assign a value to an array element that hadn't been used before. It is a little more interesting in the case of a reference which you are using for the first time, but is one of the underpinnings of creating and managing "interesting" data structures in Perl, as indeed was the case here. My pleasure, education is a large part of what PerlMonks is about. DWIM is Perl's answer to Gödel	[reply]
Re^4: hash and array mismatch by TGI (Parson) on May 10, 2007 at 20:19 UTC
I knew that autovivification would let you do things like `$foo{a}{b}{c} = 7;` I just didn't know that it worked for push and friends as well. Which is funny, because in perlreftut, it discusses the push related aspect. I know I read perlreftut a few years ago. I guess this tidbit failed to stick. For reference purposes, you can also do: `my ($foo, $bar, $baz); $foo->[1] = 92; # $foo = [92] print $bar->[0]; # $bar = []; print @{ $baz }; # DIES - $baz not in lvalue context, no autoviv.` [download] Thanks for the pointer to autovivification. I obviously didn't understand it properly when I was first learning, and never really came back to the subject. Methinks I need to carefully reread Chapter 8 of Programming Perl. TGI says moo	[reply] [d/l] [select]