First of all, please edit your node and put <code> tags around your code segments

Here is how your sub might look like (untested):

my $printsub = sub { my $node = shift; if (defined $node) { my $node_data = $node->{data}; if (defined $node_data and ref $node_data eq 'HASH') { print "node_data dir_name holds $node_data->{dir_name}\n"; print "node_data dir_vep holds $node_data->{dir_vep}\n"; } } return 0; }

I put the assignment of $node_data after the test whether $node is defined. Also there is no need to copy the hash so I changed it to a direct access of the node data. If you prefer the copy, use my %node_data = %{$node->{data}}; for the assignement instead. The test for definedness of $node should be unnecessary, the module won't call the routine without a node.

UPDATE: added defined-test of $node_data


In reply to Re: Tree::Nary n00b has questions by jethro
in thread Tree::Nary n00b has questions by Amphiaraus

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.