The problem is that he used *my* code, and when we tried to reproduce the problem, it worked well all the time. That's why I was wondering whether this is the type of undefined behaviour which "just works well most of the time". The machines are of the same type, but he uses Perl 5.8.8, while I am using 5.8.7 and 5.10 (ActiveState always). For this reason, I was interested whether the Perl programming langauge itself defines the behaviour (i.e. whether Perl is *supposed* to close the file when the local handle goes out of scope), in which case we should persuade the problem further, or whether the behaviour is unspecified/implementation dependent, in which case it makes no sense doing further research.
-- 
Ronald Fischer <ynnor@mm.st>

In reply to Re^4: Implicit closing of files by rovf
in thread Implicit closing of files by rovf

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.