I tried modifying the open command ar suggested and got the enclosed errors. Also, I'm working with Activestate Activeperl 5.6 on a Windows 2000. Also, from the syntax of the readdir example, the test is to the left of the readdir command. Does this mean I should place my file processing block to the left of the readdir command. That would be one ugly statement.
Hi. Ever try a glob? i.e.
perl -e "@files = glob( 'C:\perl\eg\*' ); print join (\"\n\", @files), \"\n\" "
[This is off a win9x platform running AS 5.6.1]
I have used similar to process directories of EDI translated data; the key being I knew what to expect in terms of no hidden files, weird file names and the like. I should think if you're ramping up for sequence processing, you'd be in that kind of a situation. Of course if you have to traverse a directory tree or two, then stick with the module File::Find
-- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
