Thanks for the hints!

If anyone is interested, my result:
my $tb = Tree::Builder->new(); find(sub { my $name = $File::Find::name; $name =~ s/^$dir//; $tb->add($name); }, $dir); my $tree = { $tb->getTree }; _transformTree( $tree ); ... sub _transformTree { my $ref = shift; ## I need sort of meta-data-enabled tree: foreach my $item (keys %$ref){ if( keys %{ $ref->{ $item } } ){ my $clone = $ref->{ $item }; $ref->{ $item } = {}; $ref->{ $item }->{name} = $item; $ref->{ $item }->{value} = $clone; # $clone = undef; # should I uncomment this? or does perl +take care of it? _transformTree( $ref->{ $item }->{value} ); }else{ $ref->{ $item }->{name} = $item; $ref->{ $item }->{value} = undef; } } }

In reply to Re: Building a nested data structure from File::Find by isync
in thread Building a nested data structure from File::Find by isync

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.