Dennis wrote:
The script has a problem when it hits a directory or filename containing
spaces.
Sisyphus [EMAIL PROTECTED] said:
Probably best if you could provide a small standalone
script (or one liner) that we can all run, and that
demonstrates the problem.
Once I've created a test
[EMAIL PROTECTED] (Chris Wagner) wrote:
I would put some print statements in there to verify that the
variables contain what u think they contain.
Hi Chris, thanks for your reply.
Yes, I had lots of prints in my original code; I snipped those out
to make my post briefer.
Another thing I
Hmm, sorry if I steal your thunder :-), but have you looked at File::Find?
And the ton of extras for variations, like File::Find::Object, ::Wanted,
::Closures, ::Rule, ::Parallel, ::Node etc etc etc...I would be
surprised if you didn't find (no pun intended ;-) something useful in
that bunch.
Kenneth Ölwing [EMAIL PROTECTED] wrote:
Hmm, sorry if I steal your thunder :-), but have you looked at
File::Find?
Hi Ken1,
Yes, indeed, I have used File::Find in the past, but ran into some
limitations.
That's why I was quite excited to hear MJD give a talk on Higher Order Perl
at.
the NA YAPC
On Wed, 24 Sep 2008, Dennis Daupert wrote:
I ran across this bit in one of Randall Schwartz's articles. He talks
about at least one of those File::Find limitations (which may have
been fixed by now, I haven't looked lately.)
You may also want to take a look at File::Next:
Welcome to the world of software development! It worked fine for years on
XYZ.. is
something I've heard so often with software that contains hidden bugs that were
never found,
often because of poor initial design. :-(
perl -w and use warnings; are your friends!
Here was my first run, with
Hi List,
I've worked with Perl on Unix for years, still a beginner on windows.
I have a script that recursively travels down a file and directory tree
and captures file stats. Works fine on Solaris.
The script has a problem when it hits a directory or filename containing
spaces.
I'll paste
- Original Message -
From: Dennis Daupert [EMAIL PROTECTED]
The script has a problem when it hits a directory or filename containing
spaces.
Hi Dennis,
I can't reproduce your specific problem:
--
C:\_32perl -e $d='C:/Users/Rob/Saved Games';print -d
I would put some print statements in there to verify that the variables
contain what u think they contain. Also Data::Dump::pp is ur friend.
e.g. print \$top: $top\n;
Another thing I noticed. Normally u want opendir DIR, $top, not $DIR. If
$DIR is undef, that code will fail. A best practice
