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}, ();
}
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.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.