Bob, boy, is that odd. Thanks for trying it out. Now, I'm really scratching my head.
-Kevin
>>> Bob Showalter <[EMAIL PROTECTED]> 07/25/03 03:03PM >>>
KEVIN ZEMBOWER wrote:
> in name?
>
>
> Thanks, Rob, for your note. I tried this:
> [EMAIL PROTECTED]:~/RapheTask$ perl t
> /cdrom
> /cdrom/JPEG Covers
> /cdrom/PDF Docs
> [EMAIL PROTECTED]:~/RapheTask$ cat t
> use strict;
> use warnings;
>
> use File::Find;
>
> find (sub{ print "$File::Find::name\n" }, '/cdrom/' );
> [EMAIL PROTECTED]:~/RapheTask$
>
> I think the failure is due to the different ways spaces in
> file names are treated in Windows vs. Unix. In Window's,
> they're allowed, in Unix, a space is a delimiter between files in a
> list.
Spaces in directory and file names are allowed in Unix. I created some
directories with spaces in them and File::Find plowed right through them,
processing their contents correctly. Something else is going on, but I'm not
sure what...
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
