Instead of the XOR, you could simply ensure that only one of the options is activated. Of course if more than one is selected in the command line arguments, the order of processing selects one by default. In some cases, ignoring user errors can be risky, but often, an appropriate order will simply result in some superfluous data output.

if ( $Add_Record ) {
    Add_Record( $args );
elsif ( $Edit_Record ) {
    Edit_Record( $args );
elsif ( $List_Records ) {
    List_Records( $args );
elsif ( $View_Record ) {
    View_Record( $args );
else {
    pod2usage(-verbose => 1);
}
__END__

[download]

--
TTTATCGGTCGTTATATAGATGTTTGCA

In reply to Re: More on Processing Command Line Arguments by TomDLux
in thread More on Processing Command Line Arguments by Ninthwave

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.