in reply to Managing structured data

Some of us may be -- uh, challenged -- (well, /me certainly is) by the lack of an explicit declaration that sect_num, eg, 4, is the z value... or that z has some other value...OR that it's the mystery-value you're referring to with the phrase "partial data." Then too, the [seq], in your problem statement, has an undefined value (Halp! Where's it come from?)

All that whining aside, why not an AoA?

my @AoA = (["seq1", 1, 1, 4], ["seq2", 2, 1, 4], ["seq3", 2, 2, 4], ["seq4", 1, 2, 4], );

Replies are listed 'Best First'.
Re^2: Managing structured data
by Anonymous Monk on Jun 11, 2012 at 13:57 UTC
    AoH is better, probably, because you can't easily see throughout your code whether you should be querying the 2nd or the 4th slot in the array to do this-or-that ... and every statement is now completely dependent on the order that you initially chose, and there WILL be a bug in there somewhere. But if the array-element is a hash, the array-element is now self-describing. Each slot is named.
      Excellent point!