Pretty shallow trees (1 level, a few subdirs, a few thousand files total) and the operation only happens once per run (a run may persist for hours to weeks or possibly months), so this does not need to be optimized at all. I was more concerned about heading off any "why doesn't your code work on my non-*nix OS?" Will trade processor cycles for programming cycles here, I think, and avoid having to know about all those DOS /flags, and similarly for any other OS somebody tries to use.
But that sort of thing--dropping to the system level for intensive file management--is good to know if I need increased performance for similar tasks in the future.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
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:
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, 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, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||