Hi wise monks

I've been wondering about the ways of dealing with command-line arguments. Are the following equally usable, as a TIMTOWTDI proof, or is there a "best practice" among them ? Do I miss some better ones ?

In the following examples I assume that the program always needs two mandatory arguments (being filenames).

#1 : Shift and Die
my $infile = shift || die usage() ;
my $outfile = shift || die usage() ;

sub usage () {
    print "usage : prog foo bar\n" ;
}

[download]
#2 : Unless and Exit
unless(@ARGV == 2)
{
    print "usage : prog foo bar\n" ;
    exit(1) ;
}

my ($infile, $outfile) = @ARGV ;

[download]
#3 : Unless and Die
die "usage : prog foo bar\n" unless (@ARGV == 2) ;

my ($infile, $outfile) = @ARGV ;

[download]

Thank you, monks.

Gu

In reply to Best practices for processing @ARGV ? by gu

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.