The main advantage of using the object-oriented IO::File interface is the ability to create new anonymous filehandles without worrying about namespace collision. Also you get a scalar that you can pass around to other subroutines without special treatment**. Furthermore, you don't have to close the filehandle explicitly before exiting the subroutine that uses it; this is done automatically when the filehandle object goes out of scope. 
{
   use IO::File;
   my $f = IO::File->new($file);
   # no need to close
}

[download]
This method is not as fast as the built-in open/close function, but it is more flexible to use, and makes the code structually cleaner and easier to work with.

** From Perl 5.6 onwards, you can do open $filehandle, .... But that is not as portable as IO::File, because the IO::File module also works on older version of Perl.

Update: I googled around and found some interesting articles in support of using IO::File -

GC vs. reference counting
Perl has a form of garbage collection, but it uses a simple scheme called reference counting. Simply put, each Perl object keeps a count of the number of other objects pointing (referencing) itself. When the count falls to zero, nothing is pointing at this object, and so the object can be freed.

Reference counting is not considered as serious garbage collection by computer scientists, yet it has one big practical advantage over full garbage collectors. With reference counting, you can avoid many explicit calls to close/closedir in code. For example:
foreach (@files)
{
  my $io = new IO::File "< $_" or die;
  # read from $io
}

[download]
This Perl code iterates over a list of @files, opening and reading each one. There is no need to close the $io file handle at the end of the loop. Because Perl uses reference counting, as soon as we reach the end of the loop, the $io variable goes out of scope, so the reference count on the file object goes to zero, and it is immediately freed (ie. closed).

As always with Perl, there's more than one way to do it. Some people like apples but others like oranges. :-)

In reply to Re: (5) Change directories, Print just the comments by Roger
in thread Change directories, Print just the comments 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.