Check for definedness rather than truth. I don't usually run into this problem, but here's a solution I just made up on the spot. Caveat lector!

my $MISC_FILE_DIR = defined($_=shift) ? $_ : die usage(); my $req = defined($_=shift) ? $_ : die usage(); my $inqfile = defined($_=shift) ? $_ : die usage(); my $sent = defined($_=shift) ? $_ : die usage(); my $status = defined($_=shift) ? $_ : die "please specify + status\n" . usage();

Another solution might be to use length to see if there's something other than an empty string there (undef evaluates to '' in a string context)

You could also lobby for the // operator to somehow make it into perl5. // is the "defined or" in perl 6 and would be used like this: my $MISC_FILE_DIR = shift // die usage();


In reply to Re: zero vs undef by duff
in thread zero vs undef by Plankton

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.