I think this is the closest to a "best solution" compared to some the others listed. Define a callback handler for your options such as: 

my $flag, @args;
my %more = ( x => 2, y => 1, z => 0 );

GetOptions(
   'x=s' => \&parse_opt,
   'y=s' => \&parse_opt,
   'z=s' => \&parse_opt,
);

sub parse_opt {
   my ($opt, $val) = @_;

   # splice additional args off @ARGV based on how many I expect
   push @args, $val, splice @ARGV, 0, $more{$opt}, ();
}

[download]

Of course, all of this is going to depend on what you want to do with things later and on whether then number of params that -x and -y take varies, etc.

Ivan Heffner
Sr. Software Engineer, DAS Lead
WhitePages.com, Inc.

In reply to Re^2: -x accepts up to 3 additional arguments by Codon
in thread -x accepts up to 3 additional arguments by tcf03

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.