when ( 'h' ) { ... }
[download]

if ( $k eq 'h' ) { ...; next }
[download]

Makes it more tail-heavy than head-heavy.

In this case, this could be cleaned up by using Getopt::Long.

use Getopt::Long qw( GetOptions );

Getopt::Long::Configure(qw( posix_default ));

GetOptions(
   'help|h|?'  => \&help,
   'verbose|v' => \my $verbose,
   'force|f'   => \my $force,
   'table|t=s' => \my $table,
)
   or usage();

@ARGV == 0
   or usage( "Too many arguments" );
[download]

Sample help and usage:

use File::Basename qw( basename );

sub help {
   my $prog = basename( $0 );
   print
"Usage:
  $prog [options]
  $prog --help

Options:
  --verbose
  -v
      ...

  --force
  -f
      ...

  --table {table}
  -t {table}
      ...
";
   exit( 0 );
}


sub usage {
   if ( @_ ) {
      my ( $msg ) = @_;
      chomp( $msg );
      say STDERR $msg;
   }

   my $prog = basename( $0 );
   say STDERR "Try '$prog --help' for more information.";
   exit( 1 );
}
[download]

This is a little more concise, I guess:

$opts{h} and HELP_MESSAGE();
$opts{v} and ++$verbose;
$opts{f} and ++$force;
$opts{t} and $table = $opts{t};
die "*** BUG: no handler for -$_.\n" for grep !/^[hvft]$/, keys %opts;
[download]

shouldn't each of $opts{...} and be prefixed with exists?

Optimising for fewest key strokes only makes sense transmitting to Pluto or beyond

Only the "$opts{t} and $table = $opts{t};" line as the rest rely on a true value.

I guess for sheer conciseness this would work:

for ( keys %opts ) {
    /h/ ? HELP_MESSAGE() :
    /v/ ? ++$verbose :
    /f/ ? ++$force :
    /t/ ? $table = $opts{$_} :
    die "*** BUG: no handler for -$_.\n";
}
[download]

Although one should first check the keys are all single letter for this case, otherwise one will get matches for words like haft, vatful and thrive.

I like how that eliminates looping.

In case it's of use, I keep a list of references on this topic: Re^2: Yet another config file editing programme : Tell me how to make it better ! (Switch/smartmatch References)

use Pod::Usage;
use Getopt::Long;
Getopt::Long::Parser->new(config => ['gnu_getopt'])
   ->getoptions(
      'help|h'    => sub { pod2usage(1) },
      'man'       => sub { pod2usage(-exitval => 1, -verbose => 2) },
      'verbose|v' => \my $verbose,
      'force|f'   => \my $force,
      'table=s'   => \my $table,
   )
   or pod2usage(2);
[download]

Give it a try.

In my Personal Nodelet, I have
• The Dynamic Duo --or-- Holy Getopt::Long, Pod::UsageMan! (the post is old enough to drink alcohol even in the USA)
• Use Getopt::Long even if you don't think you need to (not as old, but nearing "age of consent")
So, it looks like you're preaching to the choir. OTOH, I must admit that I'm in that part of the choir that needs to practice more ;-)

Well, not exactly preaching to the choir if ibm1620 wasn't using Getopt::Long and ikegami didn't mention Pod::Usage. But, I know I'm not the first to suggest it of course.

Then, there's the other faction who insist that MooseX::(something) should be used to automatically generate the commandline options. I've experimented with those and found them lacking, because command lines are inherently a thing meant to be human-friendly and I always seem to want to add some special case that the MooX::... and MooseX::... modules can't support. Getopt::Long has always given me the tools I needed to get that done. So, after lots of experimentation, I always come back to Getopt::Long and Pod::Usage. I basically consider the pair to be the only right way to start a perl script.