You can still use that method if you like, as by shifting $arg from @ARGV you remove it from the list of files that will be processed by <>. And you could still use the -two syntax if you liked, here's an example:
use strict; use warnings; my %dispatch = ( one => \&sub1, two => \&sub2, three => \&sub3, ); sub usage { print "Usage: $0 [-command]\n"; print "Available commands:\n"; print " -$_\n" for sort keys %dispatch; exit 1; } my $arg = shift @ARGV; usage() unless defined $arg; usage() unless $arg =~ /^-/; $arg =~ s/^-//; usage() unless exists $dispatch{$arg}; $dispatch{$arg}->(); sub sub1 { print "one: $_" for <>; } sub sub2{ print "two: $_" for <>; } sub sub3 { print "three: $_" for <>; }

In reply to Re^3: Using Getopt::Long to call subroutines by imp
in thread Using Getopt::Long to call subroutines by chinamox

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.