sanju7:
You could've put your data files in code tags as well, I think it would help clarify your post a little. Also, you may want to fix your indentation so that the code is easy to read. I was going to take a look at the code, but since the indentation doesn't show the program structure, I can't really read it unless I bother to download the code and reformat it. Considering it's my day off, I'm not inclined to go the extra mile.
Anyway, a couple of notes:
- Putting the key information in a hash will let you detect duplicate lines.
- You can easily open multiple files and print the records to different files to split your records out.
If I notice that the node is easier to read, or if you have any questions about what I wrote, I'll be happy to revisit the node and see if there's anything more I can offer.
...roboticus
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.