Using each for navigating hashes can clean things up a little:

use strict; use warnings; my %netMap = ( 'LSS1' => { 'LUN1' => [qw(HOST1 HOST2 HOST3)], 'LUN2' => [qw(HOST1 HOST2)], }, 'LSS2' => { 'LUN3' => [qw(HOST5 HOST6)], 'LUN4' => [qw(HOST1)], }, ); while (my @entry = each %netMap) { print $entry[0] . "\n"; while (my @lun = each %{$entry[1]}) { print " $lun[0]\n"; print " $_\n" for @{$lun[1]}; } }

Prints:

LSS2 LUN4 HOST1 LUN3 HOST5 HOST6 LSS1 LUN2 HOST1 HOST2 LUN1 HOST1 HOST2 HOST3

The down side is that you can't control the output order, it is dictated by the enumeration order returned by each.


DWIM is Perl's answer to Gödel

In reply to Re: pulling data from a complex structure by GrandFather
in thread pulling data from a complex structure by tcf03

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.