Which is a question about how to execute d:\my\onedirectory\myscript.pl
by typing `perl myscript.pl` when the current directory is c:\elsewhere.
The answer is to add d:\my\onedirectory to your path and type the
command `myscript.pl`.
The answer is *not* to associate the .pl filename extension with
perl.exe - the installer will already have done this.
http://aspn.activestate.com/ASPN/do...Winfaq4.html#How_do_I_associate_Perl_scripts_
Which is a document about how to associate the .pl filename extension
with the perl interpreter.
Associating pl with perl.exe does not help the OP achieve success with
c:\elsewhere> perl myscript.pl
when myscript.pl is in d:\my\onedirectory
which is what he said he wants to do.
Also about "Associate file types on the command line"
<exact instructions snipped>
Which *will* help the OP achieve success with
c:\elsewhere> perl myscript.pl
when myscript.pl is in d:\my\onedirectory
which is what he said he wants to do.
Note that my adviceIs *not* the same as PurlGurl's advice to associate the .pl filename
extension with the perl interpreter.
In my original response I added
PurlGurl said:
I am curious.
I provide the precise same information as you,
No you didn't.
With your having repeated what I wrote, but to a significantly
lesser degree of quality,
My advice was completely different.
why do you understand and I misunderstand?
Because I read the original posting more carefully.
Appears you are lying to readers just as McClellan lies to readers.
It is not a lie to say that associating the .pl filename extension with
the perl interpreter does not enable you to run a perl program by typing
`perl myscript.pl` when myscript.pl is not in the current directory.
Especially when the ActivePerl installer will already have made that
association.