I feel the use of Hash might not be required for your task. You have recordID which can act as an index to an array so why put them in a hash and mess up the order? You get linear access in array using index anyways an no overhead of the hash-table
That said, i would do a Matrix(nxn) (square not a requirement, dimensions might change based on num of records of course) to keep track of scores. Consider the following table
| File1rec/File2rec | 1 | 2 | 3 | 4 | 5 | 6 |
| 1 | 3 | 7 | 8 | 9 | 9 | 10 |
| 2 | 4 | 8 | 3 | 1 | 1 | 6 |
| 3 | 1 | 4 | 9 | 4 | 9 | 7 |
| 4 | 4 | 3 | 10 | 7 | 2 | 3 |
| 5 | 4 | 2 | 5 | 9 | 9 | 5 |
| 6 | 5 | 6 | 2 | 5 | 6 | 9 |
The values inside the cell are the scores. Now if you want the best matching score (max value) then a O(n) max will provide you the answer for your records and you have to do that n-times for each record in your first file.
Sorting to finx max/min is an overkill. I might be missing your porblem so please correct me if i am wrong.
cheers
SK
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.