Better done using a single hash (didn't test this, use at your own risk. Should work, though):
use strict; use warnings; my %in_files; open(my $f1, '<', 'FILE1') or die "can't open FILE1: $!\n"; while (<$f1>) { $in_files{$_} .= '1'; } open(my $f2, '<', 'FILE2') or die "can't open FILE2: $!\n"; while (<$f2>) { $in_files{$_} .= '2'; } open(my $common, '>', 'common_lines') or die "can't open common_lines: + $!\n"; open(my $u1, '>', 'unique_1') or die "can't open unique_1: $!\n"; open(my $u2, '>', 'unique_2') or die "can't open unique_2: $!\n"; for (keys %in_files) { if ($in_files{$_} =~ m/12/) { print $common $_ } else if ($in_files{$_} =~ m/1/) { print $u1 $_ } else { print $u2 $_ } }

In reply to Re: how to find common and not common lines in 2 files? by akho
in thread how to find common and not common lines in 2 files? 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.