Harry Putnam wrote:
>
> Does perl also have some compression module? My script uses tar but
> I'm having trouble because of the win habit of using spaces in file
> names.
perldoc Archive::Tar
perldoc Archive::Zip
perldoc Compress::Zlib
> In fact, on that problem is there some sort of stand
"Chance Ervin" <[EMAIL PROTECTED]> writes:
> Looks like your slashes are pointed the wrong way.
> Forward=unix
> Back=dos
>
Thanks, but don't you think if that were the problem it would fail
entirely ... but it actually creates the dir in the script.
If it were an addressing problem, I don't thin
"John W. Krahn" <[EMAIL PROTECTED]> writes:
> Harry Putnam wrote:
>>
>> I'm not used to writing perl scripts on windows. I'm having a
>> problem where a system call dies but still performs the command.
>> I don't think I understand how exit status is checked.
Thanks posters... yes you've all he
Harry Putnam wrote:
> I'm not used to writing perl scripts on windows. I'm having a
> problem where a system call dies but still performs the command.
> I don't think I understand how exit status is checked.
>
> my $target = "E:/some_dir/another_dir";
> system("mkdir $target") or die "Can't mkdi
Harry Putnam wrote:
>
> I'm not used to writing perl scripts on windows. I'm having a
> problem where a system call dies but still performs the command.
> I don't think I understand how exit status is checked.
Did you read the documentation for system()?
perldoc -f system
system() returns 0 (
Looks like your slashes are pointed the wrong way.
Forward=unix
Back=dos
--Chance
- Original Message -
From: "Harry Putnam" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Sunday, April 18, 2004 6:41 PM
Subject: (OS=winxp) system cmd dies but performs the comma
I'm not used to writing perl scripts on windows. I'm having a
problem where a system call dies but still performs the command.
I don't think I understand how exit status is checked.
my $target = "E:/some_dir/another_dir";
system("mkdir $target") or die "Can't mkdir $target: $!";
The script stop
