in reply to Win7 doesn't fill @ARGV

It's been a long time since I've been on a winboxen, so please pardon me.
But is Perl (perl.exe) within your $PATH, or %PATH, or whatever it is Win uses these days?

For example, does simply typing perl -V, produce anything || what you'd expect?

Sorry, just a bit of a guess.

--Chris

#!/usr/bin/perl -Tw
use Perl::Always or die;
my $perl_version = (5.12.5);
print $perl_version;

Replies are listed 'Best First'.
Re^2: Win7 doesn't fill @ARGV
by BrowserUk (Patriarch) on Nov 19, 2013 at 20:29 UTC

    Downvoted. Here's why:

    1. The OP says that his scripts aren't receiving arguments via @ARGV...

      How would he know that if he was unable to run the script?

    2. It is not necessary to have perl.exe in your path in order to be able to run perl scripts on windows.

      The assoc/ftype mechanism takes care of locating perl when the name of a perl script is typed at a command prompt; or .pl file is double clicked in the explorer.

    3. You say: "It's been a long time since I've been on a winboxen, so please pardon me." and then go on to give a (wrong) guess as an answer.

      Do not feel obliged to give answers on subjects you have no relevant knowledge of. There are others who will know.


    With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'
    Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
    "Science is about questioning the status quo. Questioning authority".
    In the absence of evidence, opinion is indistinguishable from prejudice.