What have you tried and where did you get stuck? Show us a little sample code and explain what's not working. Note that you can simulate files using strings for test purposes. Consider:

use strict;
use warnings;

my $file1 = <<'STR';
"111yu",erter,"00000", ,"567"
"gh6fr",erter,"00000", ,"567"
"1t76y",erter,"00000", ,"yu7"
"yu84e",erter,"00000", ,"5h7"
STR
my $file2 = <<'STR';
111yu
345cv
yu84e
STR

for my $file (\$file1, \$file2) {
    open my $inFile, '<', $file;
    print while <$inFile>;
    close $inFile;
}

[download]

Prints:

"111yu",erter,"00000", ,"567"
"gh6fr",erter,"00000", ,"567"
"1t76y",erter,"00000", ,"yu7"
"yu84e",erter,"00000", ,"5h7"
111yu
345cv
yu84e

[download]
Perl is environmentally friendly - it saves trees

In reply to Re: file comparison and splitting by GrandFather
in thread file comparison and splitting 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.