First of all, the shebang line is only the line beginning with '#!'. You remarked correctly that on Windows this has no meaning to the OS but perl will always look into that line and extract command line parameters if it contains the word perl. From this point of view it doesn't matter if you write #!perl or #!/usr/bin/perl or #!ohmegod, it's perl. On *nix this line specifies the location of the perl executable which is normally (but not always) located in /usr/bin.

Concerning the use statements, I would go for

use 5.6.0; use strict; use warnings;
as was recently discussed here. The discussion there also explains the difference between perl -w and use warnings; Your use win32; includes the win32 which provides specific functions for Windows (surprise :) but you only use it if you need some of these functions.

-- Hofmator


In reply to Re: win32 shebang by Hofmator
in thread win32 shebang by softworkz

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.