As a general thing, don't keep parallel data structures. Instead keep one data structure of items where each item has all the related parts. In this case an array of array pairs or an array of hashes:

use strict; use warnings; my @dataA = ( ['this', 0], ['array', 2], ['is', 3], ['an', 1], ); my @dataH = ( {word => 'this', index => 0}, {word => 'array', index => 2}, {word => 'is', index => 3}, {word => 'an', index => 1}, ); print "$_->[0] " for sort {$a->[1] <=> $b->[1]} @dataA; print "\n"; print "$_->{word} " for sort {$a->{index} <=> $b->{index}} @dataH;

fits the bill. The hashes version looks like overkill, but has the advantage that the code tends to be self documenting because you access the fields by name rather than by index.

Premature optimization is the root of all job security

In reply to Re: keep track of array indexes by GrandFather
in thread keep track of array indexes by Anonymous Monk

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.