As
Anonymous Monk has indicated, you have seriously abused "$x" to the point where your code deteriorates to nonsense, and IMHO, unmaintainable, probably unworkable.
I would suggest a complete overhaul, using strict and warnings, declaring meaningful variable names.
To optimize memory consumpion, read the 1000-line file into memory, then read and process each 50-line file (1000 < 50 * 50).
Please re-post when you have a new outline, and request review when you have something that compiles, but may have a specific problem (which I'm sure you will encounter). This is part of the learning process.
Software efficiency halves every 18 months, thus compensating for Moore's Law.
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.