The real problem is in how the shell interprets the command line. Rather than
passing the output of ls to your script (which can fail for very large directories)
look into just passing the directory name and then using
opendir/
readdir or
IO::Dir to
read and process the contents of the directory.
File::Copy's move
should then work fine (caveat -- I haven't tried it).
-derby
update: dws is correct, it's the output of `ls` that is messing
you up. Check your shell documentation for IFS (Internal Field Separator).
If you're convinced the backtick approach is what you want, you could
set the IFS variable to something other than whitespace (say a comma) and
then use something like `ls -m` ... but then you'd have to deal with leading
whitespace.
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.