In an attempt of guided programming:

I'd reccommed to write subroutines for each "type".

A sub dispatch will take a hash ref and call the corresponding sub for "type".

The sub type_dir will need to loop over the nested array files and call the dispatcher on them.

Show some efforts and show us your implementation for two types dir and file in a smaller SSCCE

update

With less abstraction:

You could only design sub type_dir as a recursive function calling itself since it's the only nesting one in this case.

The handling on type could be done in a if-ifelse-else block.

But IMHO that's messier and less maintainable.

---

---

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! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

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:
	&		&
	<		&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.