Thanks for your suggestions.

I could have used system "find ...", but I'd be facing the same issues ( special chars, whitespaces in filenames ), and also I'd like to avoid find ... -exec .. as this will process the files one by one. I need find, cause I need a recursive selective check to be done on all files.

>> Note that File::Copy::move doesn't allow moving more than one file at a time.<<

Hmmm ... that's bad news ... :(

My whole point is optimization, so having _all_ the files ( with potentially bad characters in their names ) available to 'mv' command, but I guess that's not possible, and doing that with shell only is a real pain.

Thank you anyway.

In reply to Re^2: Optimizing files' moving with File::Find & File::Copy modules by Anonymous Monk
in thread Optimizing files' moving with File::Find & File::Copy modules by Anonymous Monk

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.