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.
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.
It a different (but quite flexible) mechanism from *nix, but it does have advantages as well as disadvantages.
I currently use 3 differnt extensions:
In reply to Re: Path to a perl executable file on windows
by BrowserUk
in thread Path to a perl executable file on windows
by sachaer
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |