| [reply] |
| [reply] |
Another useful thing you may try is running the program from a DOS command line, this way any error message will remain up on screen so you can read it.
It's also worth pointing out why you can't run .pm files. .pl are Perl programs, entirely runnable, but .pm are Perl modules which are 'components' used in other programs, and are not programs in their own right.
| [reply] |
This used to drive me absolutely nuts.
It also goes outside of the realm of just module installation. Whenever you see a perl script you want to run on windows.
- Open your command prompt first (Start>Programs>Accessories>Command Prompt).
- Type in the command prompt 'perl '
- Drag your perl file onto the Command Prompt window.
- Press return
When you do this, the command prompt window will never close after the perl executes. Then you can run several scripts with perl and no more "oh, my god what did that just say". Also, you check a module for syntax in the Command Prompt too. Yep, try it. type perl theModule.pm. If the module is all good, the Win Command prompt will return with no errors. I tell you this in hopes that you will see that 'perl file.pl' tells windows to use perl to run file.pl. BTW 'c:/Perl/bin/perl c:/file.pl' works the same way.
P.S.When you drag your file into the Command console, the absolute file path is pasted in, surrounded by quotes. Just make sure you have 'perl ' before you drag or it may not run under perl.
jtrue
| [reply] |
| [reply] |