in reply to #!/usr/bin/perl -w

for most Windows perl applications (console, GUI) this is not necessary. But if you use apache as a local webserver you need a she bang unless you edit your http.conf file to recognize .pl.

In general, at least with an active state install your perl is placed on the path. so:

#!perl

is enough to call your interpreter. #!/usr/bin/perl will cause a 500 server error on Apache for windows. So if you test CGI's at home on windows and deploy to a UNIX server, it's something that you need to deal with.

Replies are listed 'Best First'.
Re: Re: #!/usr/bin/perl -w
by mr2 (Friar) on Jul 18, 2002 at 20:06 UTC
    yeah ... you don't realy need any path at the begginnig of perl script under windows (activestate perl)... if your file name is *.pl windows uses assoaciations that alow to forget about the path to perl interpreter.