Re: Best practices for processing @ARGV ?

#1 is buggy. A file name "0" will incorrectly die. The (not so pretty) solution:

defined(my $infile  = shift) || die usage();
defined(my $outfile = shift) || die usage();
[download]

I find #2's unless (@ARGV == 2) harder to read than if (@ARGV != 2).
I'd print usage to STDERR, so I prefer die("message"), warn("message") and print STDERR ("message") over #1 and #2's print("message").

Comment on Re: Best practices for processing @ARGV ? Select or Download Code

Replies are listed 'Best First'.
Re^2: Best practices for processing @ARGV ? by Hue-Bond (Priest) on Dec 13, 2005 at 01:39 UTC
I find #2's unless (@ARGV == 2) harder to read than if (@ARGV != 2) Me too but, as a non-native english speaker, I find it much easier to translate "unless" as if it were "if not". -- David Serrano	[reply]