I would do it something like this:
my %f1; while (<FILE1>) { chomp; my @fields = split /\|/; my @col3 = split /\s+/, $fields[2]; $f1{lc $fields[0]} = [$col3[0], $col3[2]]; } while (<FILE2>) { chomp; my @fields = split /\s*\|\s*/; my $name = lc $fields[0]; print "line $.: Name $fields[0] "; if (exists $f1{$name}) { if ($fields[1] == $f1{$name}[0] && $fields[3] == $f1{$name}[1] ) { print "matched.\n"; } else { print "found but not matched.\n"; } } else { print "not found.\n"; } }
Which, in your case, would give output of:
line 1: Name David matched. line 2: Name harry found but not matched. line 3: Name harry found but not matched.
But I don't really know what you are trying to accomplish, or whether you want case insensitivity (remove the lc's if you don't).

In reply to Re: Matching two files by gamache
in thread Matching two files by thickice97

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.