If you already know that a certain type of error will not occur, why bother doing extra programming to prevent it?
Encountering undef values in the array was also a case of "a certain type of error will not occur". But it did, due to the one-off error. But supposing there was a valid reason to be seeing undef's in the arrays; you don't want to turn off other warnings that might indicate different errors.
Computers don't just get up in the morning and decide to give you letters instead of numbers as an April Fool's Day joke.
Sure they do; we get it reported here all the time, with code that looks like:
sub foo { while (<INPUT>) { ... } } for (@array_of_numbers) { ... foo() ... }

In reply to Re^4: A better way than || by ysth
in thread A better way than || 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.