Quote:
|
Originally Posted by Thorn
It isn't a problem, per se. The EXE just doesn't know what to do, as you haven't given it an argument.
Simply run PERL from the command line with an argument like it was intended:
C:\> \perl\bin\perl myscriptname.pl
or:
C:\perl\bin> perl myscriptname.pl
|
I use ActivePerl as said previously. I've also used cygwin perl, but don't like it because you have to build/compile all the modules.
I put the perl\bin directory in my path, then I can run the files by just typing the scriptname.
c:\>script.pl
If you want ActivePerl to co-exist with cygwin Perl, I think it can be done. You can leave perl off your path, then have a couple .bat files to update your path for either version of Perl as desired.
I love ActivePerl because of the PPM. Further, they now have the pcap modules available directly. Check my
perl sniffer pages for details.