I'll note that in what you posted above there's no reason to read NAMES into memory - in fact, if the order of names in NAMES is significant, what you do will cause a problem.
When I read the post, my impression was that the order of values in NUMBERS was what the poster wanted preserved, and so would have said:
#!/usr/bin/perl
use strict;
use warnings;
open (NUMBERS, '<', "numbers.txt") or die "Unable to open numbers.txt
+for reading : $!";
open (NAMES, '<', "names.txt") or die "Unable to open names.txt for re
+ading : $!";
my @namevals = map {chomp; [split /\t/ , $_ , 2]} <NAMES>;
while (<NUMBERS>)
{
s/\s//gs;
my $current = $_ + 0;
map {print $_->[0]," matched $current\n"
if (abs($_[1] - $current) <= 0.5);}
@namevals;
}
If runtime is an issue, namevals could always be split into a hash of lists based on the floor() of the given value - then, when comparing, you'd only compare against the two lists that contained namevals near the target value.
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.