Getopt::Long leaves any unknown data that it finds in @ARGV alone. So you could process whatever's left in @ARGV yourself after sending it through GetOptions():
my($help,$backup,$upd_sybase,$silent); GetOptions('help|h!' => \$help, 'b!' => \$backup, 'u!' => \$upd_sybase, 's!' => \$silent); # assuming it's always key1 value1 key2 value2 in argument list my %other_args = @ARGV; # if your arguments are positional, do this: # my($server,$password) = @ARGV; # called like this: ./foo --silent server bar password blah # yields: # $silent == 1 # $other_args{server} eq "bar"; # $other_args{password} eq "blah";
Update: Added an example for positional arguments since the OP seemed to maybe have wanted that --Brian

In reply to Re: Mixing command line arguments by bpphillips
in thread Mixing command line arguments by Anonymous Monk

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.