You should really be able to figure out the I/O changes for yourself, but to ensure you follow best practice change:

open my $in1, '<', \$File1;

[download]

to:

open my $in1, '<', $file1 or die "Can't open '$file1': $!\n";

[download]

where $file1 contains the path to input file 1. Do the same for $file2. Add:

open my $out, '>', $fileOut or die "Can't create '$fileOut': $!\n";

[download]

and change the print statement to:

    print $out $line1, ',', (split ',', $line2)[-1];

[download]

(my $line2 = <$in2>) reads a line from $in2 and assigns it to the variable $line2. or last; exits the loop if $in2 contains fewer lines than $in1.

Perl is the programming world's equivalent of English

In reply to Re^3: Solve the large file size issue by GrandFather
in thread Solve the large file size issue by Vkhaw

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.