When writing a script for command-line use, I try to make it easy for the user to get enough information about the expected / allowed args and options. Given your very limited example, I would tend to do it like this:
my $usage = "Usage: $0 [path]\n default: value of env.variable LOGS_EV
+\n";
my $destdir;
if ( @ARGV ) {
$destdir = $ARGV[0];
}
elsif ( $ENV{'LOGS_EV'} ) {
$destdir = $ENV{'LOGS_EV'}
}
else {
warn "Please supply a path or set LOGS_EV\n\n";
die $usage;
}
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.