Since you are merging the hashes, do you really need two of them? Also, it seems that the only critical part of the line is the word at the begining, so you can just split that off separately and save the rest of the line in a single variable.

use warnings; use strict; my %filehash; my @files = qw(F1.dat F2.dat); for my $filename (@files) { open my $filehandle, '<', $filename or die "Can't open $filename $ +!\n"; while (<$filehandle>) { my ( $word, $remainder ) = split ' ', $_, 2; $filehash{$word} = $remainder; } close $filehandle; } open my $merged, '>', 'merge.dat' or die "Can't open merge.dat:$!\n"; for ( sort keys %filehash ) { print $merged "$_ $filehash{$_}"; }

Update: changed split parameter to ignore any initial whitespace


In reply to Re: file merge problem by thundergnat
in thread file merge problem 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.