I'd like to address the assertion that for forward iterating you need one hash and for reverse iteration, you need another. This seems to me like you would have a hash of hashes, built as such: 
my %datastructure = (
    forward_iteration => {
    },
    reverse_iteration => {
    },
);

[download]
This seems wasteful to me. Instead, why not have something like 
my %datastructure = {
    elem1 => {
        forward => 1,
        reverse => 2,
    },
    elem2 => {
        forward => 2,
        reverse => 1,
    },
};

[download]
This way, if you want to change your code to add a new ordering mechanism (which happens more often that I'd like), you just add another value to each element's hashref of orderings. And, building the ordered-hash is more obvious, because you're doing something like 
$datastructures{$elem} = {
    forward => forward_val($elem),
    reverse => reverse_val($elem),
    other_way => other_way_val($elem),
}

[download]
Just a thought. :-)

------
We are the carpenters and bricklayers of the Information Age.

Don't go borrowing trouble. For programmers, this means Worry only about what you need to implement.

In reply to Re: Using a hash for an ordered set can make sense by dragonchild
in thread Using a hash for an ordered set can make sense by stefp

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.