I think that you are basically agreeing with me, quibbles about syntax aside.

I was reacting to the idea of "out of memory". That will not happen if the huge file is processed line by line after the FILE open instead of being stored as an array and then processed in memory.

There could be some other problem here that the OP did not show and is completely unknowable to us because it wasn't shown. A 100MB file even under Win32, version XP should be easy to do, even as an in memory array. A FILE handle should not be "re-opened" with an append for multiple writes - that can cause memory problems with the file system. Keep the file handle open and just continue writing.

In reply to Re^4: Out of Memory Error : V-Lookup on Large Sized TEXT File by Marshall
in thread Out of Memory Error : V-Lookup on Large Sized TEXT File by TheFarsicle

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.