That's good advice, "Always use strict." Unfortunately, you've fallen almost at the first hurdle by forgetting to use my when opening your lexical filehandle. It is also recommended practice to test for the success of the open statement (and close as well) and to use it's three argument form.

open my $fIN, q{<}, q{msgcount.txt}
   or die qq{open: msgcount.txt: $!\n};

[download]

Failing to test for success can lead to "readline() on closed filehandle $fIN at myscript.pl line nnn" errors if, say, you mis-type the path or the file has been deleted or ...

I hope this is of interest.

Cheers,

JohnGG

In reply to Re^2: Parsing a text file by johngg
in thread Parsing a text file by nimajneb

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.