As a suggestion to avoid this kind of problem, if you use a lexical variable as a file handle instead of a bareword, when the variable goes out of scope, Perl will automatically close the file for you. e.g. 
open my $file, "<", $filename # use lexical variable

open FILE, "<", $filename # use bareword.

[download]

So if you have a subroutine; 
sub foo {
  my ($filename) = @_;
  open my $file,  "<", $filename or die "blah :$!\n";
  while (<$file>) {
    # etc
  }
  # explicit call to close not needed.
}

[download]
The file will be closed at the end of the foo subroutine. If you want the file handle then return it.
And if you aren't using a lot of subroutines but want this behavior, simply start a new block.

In reply to Re: Debug openings and closings by bruceb3
in thread Debug openings and closings by senduran

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.