blink,
I know it can be confusing, but I think you want getopts from Getopt::Std instead. Here is a fully functional template for you. 
#!/usr/bin/perl -w
use strict;
use Getopt::Std;

my %Opt;
Get_Args();

sub Get_Args {
    my $Usage = qq{Usage: $0 [options]
        -h : This help message.
        -a : BOGUS - requires argument if used
        -A : BOGUS
        -b : BOGUS
    } . "\n";

    getopts( 'ha:Ab' , \%Opt ) or die $Usage;
    die $Usage if $Opt{h};
    die "You did not enter any options\n" if ! %Opt;
    if ( exists $opt{a} || exists $opt{A} ) {
        if ( ! ( exists $opt{a} && exists $opt{A} ) ) {
            die "You must use -a and -A together\n";
        }
    }
}

[download]
Cheers - L~R

In reply to Re: Boundary conditions with Getopt::Std by Limbic~Region
in thread Boundary conditions with Getopt::Std by blink

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.