Another important change is to control flow logic and code organization
open ... or die Error(...);
open ... or return ErrorPage(...);
If you can't open the file, don't try to read from it or write to it, end the subroutine (the code should be in subroutines
Don't generate your pages by interleaving print statements, make subroutines, so your program is
Main( @ARGV );
exit( 0 );
sub Main {
my $q = CGI->new;
print SomeKindOfPages( $q );
}
sub SomeKindOfPages {
my( $q ) = @_;
...
my( $headers, $body ) = ShippingEstimator( $q , ... );
return $headers, $body;
}
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.