I know I already posted my "whys" for the bang line, but just to re-emphasize -- I 
can't tell you how much mileage I've gotten out of the Cygwin environment under 
Windows NT/2000, replacing the Cygwin perl.exe (which is still very good) with ASPerl. 
 Surely some readers here have already discovered it, but for those that have not, 
give Cygwin a whirl: www.cygwin.com

After Cygwin install, "mv /usr/bin/perl.exe /usr/bin/cygperl.exe" and "ln -sn 
/path/to/aspn/perl.exe /usr/bin/perl.exe" and you are set.  Then you DO need the bang 
path in your Cygwin bash shell under Windows NT/2K.

Your Win32::Lanman has been invaluable on this projext, Jenda.  Thanks for writing it. 
 I've not been in the Perl/Win32 environment long, but when I went looking for a 
solution, all the "references" (ha!) I could find when researching a solution were to 
your Lanman.  http://Jenda.Krynicky.cz/perl is a permanent part of my PPM repository 
list now... (as is David Roth's PPM repository site.)

Chris
-----
Chris Olive
[EMAIL PROTECTED]

---------- Original Message ----------------------------------
From: "Jenda Krynicky" <[EMAIL PROTECTED]>
Date: Tue, 23 Apr 2002 13:53:00 +0200

>From: "Philip Morley" <[EMAIL PROTECTED]>
>> Also, as an additional point, in the extract of the script you
>> provided, what is the point of this line:
>> 
>> #!/usr/bin/perl -w
>> 
>> if you are using a Windows Operating System, not a Unix/Linux one?
>
>1) the fact that the default shell (cmd.exe) or the explorer (in case 
>of doubleclick) ignores the shebang line doesn't mean all programs 
>do. It may be used by some Unixie shell he uses or by the 
>Windows version of Apache.
>
>2) Perl itself does care about that line. And exits if it finds 
>something that doesn't match /perl/i. Try to run this script with 
>Perl.exe:
>
>       #!/bin/sh
>       print "Hello world\n";
>
>3) Perl processes that line and uses whatever options you 
>specified on the line. This means that
>
>       c:\> perl
>       #!perl -w
>       print "x=$x\n";
>       ^Z
>
>and
>
>       c:\> perl -w
>       print "x=$x\n";
>       ^Z
>
>wil give you the same warnings.
>
>This means that if you start your script with 
>       #!perl -w
>it will be run with warnings turned on even if the user doesn't ask for 
>it ;-)
>
>Jenda
>
>=========== [EMAIL PROTECTED] == http://Jenda.Krynicky.cz ==========
>There is a reason for living. There must be. I've seen it somewhere.
>It's just that in the mess on my table ... and in my brain
>I can't find it.
>                                       --- me
>_______________________________________________
>Perl-Win32-Admin mailing list
>[EMAIL PROTECTED]
>To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
>
_______________________________________________
Perl-Win32-Admin mailing list
[EMAIL PROTECTED]
To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs

Reply via email to