Yes. Use a hash. If file1 has more than 10000 or 100000 lines then you need a disk-based hash or database, but normally you just use something like this:

use strict; use warnings; my %seeninfile1; open FH,"<",$file1 or die "Can't open $file1: $!\n"; while (<FH>) { $seeninfile1{$_}++; } close(FH); open FG,"<",$file2 or die "Can't open $file2: $!\n"; while (<FG>) { ($key,$number)= split; if ($seeninfile1{$key} { #do whatever you want to do if key is not in file1 } else { #do whatever you want to do if key is in file1 } } close(FH);

Using a hash means you will read both file1 and file2 only once. Your code reads in file1 once for every line(!) of file2. Your code will quickly slow down when your files get bigger.


In reply to Re: list lines not found in config (while+if) by jethro
in thread list lines not found in config (while+if) by tangledupinperl

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.