I've never heard of Tree::Nary before. (Searches.) Hrm, based on http://cpanratings.perl.org/dist/Tree-Nary and what I understand about how Perl works internally, I wouldn't suggest using it. Instead I would suggest thinking in terms of native Perl data structures, using references to build more complex ones. That will be less code, should perform better, and will save memory. Read References quick reference if you need to learn how to build more complex references.

Still if you wish to persist in this approach, the answer to your first question is that you should learn how to handle references. While you're learning, Data::Dumper may be a good friend. I would handle your second question by turning each entry into a small anonymous hash, and I'd collect an array of those. Then post-process that array. For instance sort it by directory then group that up. (Note that I would not organize it using [cpan://Tree::Nary, but you could if you wanted to.) My first answer to your third question is that you should not be planning on parallelizing your code until after you have a proven performance problem. If you do, then as I said I would organize the data by sorting it first then running some grouping logic on it.

In reply to Re: Tree::Nary n00b has questions by tilly
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.