I'm on a Windows 2000 environment - and yes, I agree that using the PERL
conventions would be best. Unfortunately, there is a specific request for
this command to be used in this basic format. I've used the command in a
shell script (.sh) and it works fine, but no luck in PERL.
If you have any more suggestions I will be glad to try them - if not, I
thank you for your reply.
K
Rob Dixon wrote:
> <[EMAIL PROTECTED]> wrote:
> By the way,
> > I'm having a problem when redirecting output from a system call to a text
> > file. A good example would be:
> >
> > command.com /c dir /O /a-d /s > dir.txt
> >
> > When I run this directly from the command line I will get the full path
> > structure in the output file. When I call this from a perl script in the
> > form:
> >
> > system ('command.com /c dir /O /a-d /s > dir.txt');
> >
> > the output to the text file concatentates directory names longer than 8
> > characters to 8 characters. My desire is to have the output explicitly
> > state the full path rather than the concatenation.
> >
> > Any ideas what I need to do to overcome this problem?
> Which Windows system are you working on? On my XP and 98
> systems this call returns the 8.3 file name in the first few
> characters of each column and the full file name at the end,
> whether it's a directory or a regular file.
> Anything that's written in native Perl is best in my book, so
> you really should read about reading directories with
> perldoc -f opendir
> perldoc -f readdir
> perldoc -f closedir
> But if you just need to traverse a directory tree then take a
> look at
> perldoc File::Find
> HTH,
> Rob
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
<http://learn.perl.org/> <http://learn.perl.org/first-response>
