Is my @ARGV broken?

ibanix has asked for the wisdom of the Perl Monks concerning the following question:

I seem to be having some trouble with a ActivePerl installation. In particular, it doesn't seem to handle @ARGV correctly. Here's my test code:

use strict;
use warnings;

my $first = shift(@ARGV);
my $second = shift(@ARGV);
my $third = shift(@ARGV);

print "$first\n";
print "$second\n";
print "$third\n";
[download]

On this server, running it looks like this:

D:\argv_test.pl I like code
 I like code


D:\
[download]

On the other hand, it works as expected on my workstation:

C:\>argv_test.pl I like code
I
like
code

C:\>
[download]

Both installations are vanilla ActivePerl v5.6.1.
Any ideas?

Thanks!
ibanix
$ echo '$0 & $0 &' > foo; chmod a+x foo; foo;

Comment on Is my @ARGV broken? Select or Download Code

Replies are listed 'Best First'.
Re: Is my @ARGV broken? by rbc (Curate) on Jan 17, 2003 at 22:43 UTC
	[reply]
Re: Re: Is my @ARGV broken? by ibanix (Hermit) on Jan 17, 2003 at 22:55 UTC
Well, this was definately the related problem. I changed the ftype to the full path to perl.exe, and hey presto, it works as expected: `ftype perl=D:\perl\bin\perl.exe %1 %*` [download] Ever feel dumb? I sure do! I even wrote a tutorial on this! Doh! Thanks for the help! ibanix `$ echo '$0 & $0 &' > foo; chmod a+x foo; foo;`	[reply] [d/l] [select]
Re: Re: Is my @ARGV broken? by ibanix (Hermit) on Jan 17, 2003 at 22:48 UTC
Interesting. I had set mine up previously. Here's what it looks like: `D:\>assoc .pl .pl=perl D:\>ftype perl perl=perl.exe "%1" "%*"` [download] ibanix `$ echo '$0 & $0 &' > foo; chmod a+x foo; foo;`	[reply] [d/l] [select]
Re: Is my @ARGV broken? by ibanix (Hermit) on Jan 17, 2003 at 22:45 UTC
Update: I just tried this: `D:\argv_test.pl "I like code" I like code D:\` [download] So it only works with double quotes now? ibanix `$ echo '$0 & $0 &' > foo; chmod a+x foo; foo;`	[reply] [d/l] [select]
Re: Is my @ARGV broken? by Marza (Vicar) on Jan 17, 2003 at 22:39 UTC
Wierd! I ran it on a w2k server and it displayed right! But that was with 5.8.0	[reply]