And of course, if you want the perl scripts to just run without invoking the interpreter directly, you can associate all .pl files with perl.exe. This is done automatically with the ActivePerl MSI install. Additionally, you can add .pl to your PATHEXT environment variable so that you can invoke your scripts without necessarily using the extension (although the extension still needs to be there for the file to work)
-----Original Message----- From: Shawn [mailto:[EMAIL PROTECTED]] Sent: Tuesday, June 18, 2002 2:04 PM To: [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: Re: running perl scripts on Windows > > On Win2K, from the command line, the she-bang means absolutely nothing. > > It's not until you try to run it from a server that the she-bang comes > > into play... I think it is the same across all win32 platforms... > > The previous op was correct. The first line is parsed for switches, unix or > win32. As a side note, with unix, its only when you make the file > executeable that the shebang serves any other purpose. Oops, forgot about the switches... But, if you have no switches, the shebang is not needed if the command is run like: perl myscript.pl. Shawn -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
