hextor look at that good example by
toolic and pay attention to the
GetOptions ... or die; part.
This is very important because you dont want your program to execute with wrong or not accepted args.
Personally i ended using everytime yet another idiom, even more cautious:
use Getopt::Long;
use Pod::Usage; # if you have documentation embedded is better
unless (GetOptions( "option=s" => \$option ... )) {
pod2usage(-verbose => 1,-exitval => 'NOEXIT'); # automatic u
+sage printing (if you have an usage section in POD)
&wait_for_input; # if the prog
+ was opend in a 'double click' fashion there is no time
# to review e
+rrors, if so you can just use something like:
# sub wait_fo
+r_input{
# print "\n
+\nPress Return when ready\n";
# while (<S
+TDIN>){last if $_ }
# }
exit; # now you can
+ exit or die with yet another error string
}
HtH
L*
There are no rules, there are no thumbs..
Reinvent the wheel, then learn The Wheel; may be one day you reinvent one of THE WHEELS.
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.