I was referring to being wary when $line=<FH> is used on its own. To illustrate:
$ perl -e 'print "with_ending\nno_ending"' > a.txt
$ perl -MData::Dumper
    open(FH, "<", "a.txt") or die $!;
    my $line1 = <FH>;
    my $line2 = <FH>;
    my $line3 = <FH>;
    close FH;

    $Data::Dumper::Useqq = 1;
    print Dumper [$line1, $line2, $line3];
__END__
$VAR1 = [
          "with_ending\n",
          "no_end",
          undef
        ];

[download]

We see that there is a possibility that a line read ($line3 in this case) may return undef. That's what I meant: we need to be wary that a line read will not always return defined.

In reply to Re^4: File Reading and Closing confusion by repellent
in thread File Reading and Closing confusion 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.