If your test.txt file is long, it may make sense to pre-compile the entries for faster searching. Also, you want to make sure to use \Q and \E to make sure wildcards in the file names don't get expanded.

Also, please check return codes on system calls such as open().

Consider something like the following: 
my @patterns;
foreach my $pattern (`ls`) {
    chomp $pattern;
    push @patterns, qr/\Q$pattern\E/;
}

open(IN,"test.txt") or die "Can't open test.txt: $!\n";
while(my $line = <IN>) {
    chomp $line;
    foreach my $pattern (@patterns) {
        print "Match found\n" if $line =~ $pattern;
    }
}

[download]

In reply to Re: Search List by sachmet
in thread Search List by pglenski

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.