Because you've used a for loop, the first instance of <FILE> reads the entire file into memory (the place where you've put the read is in list context and perl slurps in list context). The second read occurs at the end of the file, so you get undef. If you really want to do this, use a while loop instead: 

while (my $line = <FILE>) {
   my $x = <FILE>;
   # ...
}

[download]
The conditional of a while is in scalar context, so only one line at a time will be read.

It's interesting to note that perl6 will change this common idiom such that a for loop does the Right Thing. (for those interested, it would look something like this: for =$filehandle -> $line { my $x = =$file_handle; ... } or when you're going to do the same as while (<>) { ... } in perl5, it's for =<> { ... } in perl6.)

duff

In reply to Re: nested <FILE> read returns undefined? by duff
in thread nested <FILE> read returns undefined? by argv

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.