Re^2: Optimizing files' moving with File::Find & File::Copy modules

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.

Comment on Re^2: Optimizing files' moving with File::Find & File::Copy modules Select or Download Code

Replies are listed 'Best First'.
Re^3: Optimizing files' moving with File::Find & File::Copy modules by JavaFan (Canon) on Nov 17, 2009 at 10:44 UTC
`system "find $dir1 -type f -exec mv -t $dir2 '{}' '+'";` [download] Spaces and special characters aren't a problem as `find` doesn't invoke a shell. And by using a `+` instead of a `;`, the `-exec` will behave as `xargs`. You may need GNU implementations of `find` and `mv`, I do not know whether `mv -t` is a POSIX requirement, nor do I know that of `find -exec command` . But I doubt it's much of a problem to get those GNU tools running on a platform that supports perl.	[reply] [d/l]
Re^4: Optimizing files' moving with File::Find & File::Copy modules by runrig (Abbot) on Nov 17, 2009 at 17:16 UTC
If he doesn't have that implementation of find, and there are spaces in filenames, the array form of system will handle them: `my @files = <$dir1/*>; system("mv", @files, $dir2);` [download]	[reply] [d/l]
Re^5: Optimizing files' moving with File::Find & File::Copy modules by JavaFan (Canon) on Nov 17, 2009 at 17:27 UTC
Eh, no. `<$dir1/*>` doesn't distinguish between files and directories, it doesn't find files whose name start with a dot, and doesn't recurse into directories below $dir1. And if there are many files, you may run into system limits - most OSses have a limit on the number of arguments (and total size of the arguments) `exec` can take. (`E2BIG`).	[reply] [d/l] [select]
Re^6: Optimizing files' moving with File::Find & File::Copy modules by runrig (Abbot) on Nov 17, 2009 at 17:42 UTC