Don't steal. Stolen goods often have nasty baggage. In this case strict is missing, there is no error checking on the opendir, package variables rather than lexical variables are being used and the various open issues that may face the OP are not addressed. A better version of the code is:

use strict;
use warnings;

opendir my $scanDir, $directory or die "Unable to open directory $dire
+ctory: $!\n"
my @files = grep /^R/, readdir $scanDir;
closedir $scanDir;

for my $filename (@files) {
    open my $inFile, '<', "$directory/$filename" or die "Can't open $d
+irectory/$filename: $!";
    ...
    close $inFile;
}

[download]
True laziness is hard work

In reply to Re^2: Reading specific files by GrandFather
in thread Reading specific files by molson

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.