in reply to Path to a perl executable file on windows

There is no need to use the hooky FindBin method. :)

If the scripts are in a directory in your path, there are a couple of further steps needed.

  1. Tell the OS that you wish it to consider .pl (or whatever extension you choose) to be considered and 'executable' file.

    You do this by adding your chosen extension to the PATHEXT environment variable. The best way is to do this through the Start->Settings->ControlPanel->System-> Environment tab. Where you can choose to make this so system wide (if you have appropriate privaledges) or on a user by user basis.

  2. Tell the OS what executable you which to be invoked for .pl files through the usual ftype and assoc mechanism.

It a different (but quite flexible) mechanism from *nix, but it does have advantages as well as disadvantages.

I currently use 3 differnt extensions:

  1. .pl for 5.6.1 scripts.
  2. .pl8 for 5.8 scripts.
  3. .plt for my experimental (test) build of perl.

Examine what is said, not who speaks.
"Efficiency is intelligent laziness." -David Dunham
"When I'm working on a problem, I never think about beauty. I think only how to solve the problem. But when I have finished, if the solution is not beautiful, I know it is wrong." -Richard Buckminster Fuller


Replies are listed 'Best First'.
Re: Re: Path to a perl executable file on windows
by sachaer (Initiate) on Jul 14, 2003 at 20:31 UTC
    Thanks to all who replied to my question.

    I tried the easiest answer, which is changing the PATHEXT environment variable and it works very well!!! :)