in reply to Looping Over Hash Skips an Element?

I'm wondering why you need a hash. You are indexing anyway so why not just have two arrays, one for the keys and one for the values.

Another thing I notice is that your keys contain an index. Why not use that number as the index for an array that holds the values? When you need to print you can add the Gi3 part in the print statement. An array would let you do the sum of 8 (or more) values at a time. $sum=$a[$n]+$a[$n+1]+ ... You could use a c style for loop to iterate through every 8th index.

Replies are listed 'Best First'.
Re^2: Why not using an array?
by pklausner (Scribe) on Jan 10, 2012 at 13:22 UTC
    From them names I guesstimate he populates this table from the SNMP interface MIB. The index of the ifTable is not necessarily contiguous. Some devices give you 1,2,3.. then jump to 100 or even 1000. So that is not practical as array index. I had the same problem and solved it with hashes plus a custom sort function: 
    sub sort_by_intf # sort interface alpha/number name mixture properly
{ my $A = $a;    # just turn any number into a 0004 digit one
  my $B = $b;
  $A =~ s/([0-9]+)/ sprintf "%04d",9999-$1 /ge;
  $B =~ s/([0-9]+)/ sprintf "%04d",9999-$1 /ge;
  $B cmp $A; # reverse order happens to be useful here:
}            # Tun0, Ser1, Port-channel2, Gi3, Fa4, Eth5

    [download]
    Then whenever you loop over the keys, just sort them with that function like so: 
    for (sort sort_by_intf keys %ifSpeed) {
  printf "intf: %s,  speed: %d\n" $_, $ifSpeed{$_};
}

    [download]
[reply]
[d/l]
[select]

In Section Seekers of Perl Wisdom