Sounds like it is time to refactor.

First of all I would strongly recommend cutting down on the globals. For an explanation of why see RE (tilly) 3: redeclaring variables with 'my'. After that, well I don't like having to keep multiple arrays in sync. It is too easy to get it wrong. Have you considered using anonymous hashes? An array of anonymous hashes with information about the title, sector, and the data is harder to make mistakes with. If you want you can even make them into objects and hide them off in some class.

If you try you can probably remove all need to ever think about what position in a particular data structure your data is. Push that accounting down to Perl and your program will be much more reliable, easier to write, and if that wasn't enough it will be easier to read as well. :-)


In reply to Re (tilly) 1: Foreach Complications by tilly
in thread Foreach Complications by ImpalaSS

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.