coldfingertips,
I seriously question using numeric keys soley on the basis of sorting or the need to re-order them when they are deleted, but I think this will do what you want: 
#!/usr/bin/perl -w
use strict;

my %hash = (1 => 'foo', 2 => 'bar', 3 => 'asdf', 4 => 'blah', 10 => 'w
+oah');
delete $hash{3};

FixHash(\%hash);
print "$_ : $hash{$_}\n" for sort { $a <=> $b } keys %hash;

sub FixHash {
    my $hashref = shift;
    my $index = 0;
    for my $key ( sort { $a <=> $b } keys %$hashref ) {
        $index++;
        next if $key == $index;
        $hash{$index} = delete $hash{$key};
    }
}

[download]
I would probably look at one of the modules for sorted hashes like Tie::IxHash and Tie::Hash::Sorted or use an array.

Cheers - L~R

In reply to Re: rebuilding hashes by Limbic~Region
in thread rebuilding hashes by coldfingertips

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.