Maybe this example is what you're looking for?
my @script; GetOptions( ... 'call=s' => sub { push @script, [ call_method => $_[1] ] }, 'eval=s' => sub { push @script, [ do_eval => $_[1] ] }, 'out|o=s' => sub { push @script, [ output => $_[1] ] }, '<>' => sub { push @script, [ process_tpl => $_[0] ] }, ) or pod2usage(2); ... sub call_method { ... } sub do_eval { ... } sub output { ... } sub process_tpl { ... } # All the global options are taken care of. Now execute the "script o +ptions" # in the order they were given. for (@script) { my ($method, @args)= @$_; $method= main->can($method) or die 'bug'; $method->(@args); }

In reply to Re^5: Closed:how to argparse same option to array instead of overwrite by NERDVANA
in thread Closed:how to argparse same option to array instead of overwrite by vincentaxhe

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.