roboticus has good points. I would add the following only as an additional consideration: 

use strict;
use warnings;

main();

# always have an exit from a script, it will save you grief!
exit;

sub main {

    ... # do some really cool stuff here

    # always have a known return value, just falling off the end WILL 
+bite
    # bite you someday.
    return;
}

__END__

[download]

The use of exit and __END__ can prevent unexpected additions to your script for one reason or another. It is also handy to have all your POD (you do document your code, right?) after the __END__ statement.

It helps to remember that the primary goal is to drain the swamp even when you are hip-deep in alligators.

In reply to Re: creating a perl entry-point by boftx
in thread creating a perl entry-point by morelenmir

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.