Sounds like you need a tree data structure. I'd stick with the hash thing, and make a key called 'dependencies' that points to an anonymous hash. In that second hash, the key would be the dependency name, and the value would be a reference to the dependency hash.
You'll have to figure out some way to add the references as you add dependencies. Keep another hash around with needed dependencies as keys, and as values, an anonymous array of references to objects that depend on them. (Is this starting to hurt your head yet?) When you add a new file, look to see if it can be added to those hashes.
Once you've added all the files, iterate through the hashes, sorting them by least number of dependencies.
You could also, in step two, record *which* dependencies a file fulfills, and build an inverted tree.
I'd use objects in this case. It'd simplify things like linking.
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.