A few tips:

Don't use FatalsToBrowser in production code, it's a useful tool for testing, it's a potential source for hackers to gather information of your server.

Separate perl-code and html. You can use templating solutions for that like Template (there are more templating solutions, look around on permonks,cpan).

For separating into subroutines, there are no strict rules, but try to split it up in places you think are logical. For instance a CGI script with several states could be split up in one subroutine per state. Experiment with it, see if you can find pieces in your code that look reusable, so if you make them into a subroutine you could use this subroutine later on in another script.

In reply to Re: Perfecting index.pl some more! by eXile
in thread Perfecting index.pl some more! by Nik

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.