Thanks for the responses, and special thanks to tilly for the code! So while I play with tilly's code, another sort of followup question: It seems that everyone thinks that my script is biting off more than it can chew (or chomp) so to speak. What if instead of using 
$text=<INFILE>;

[download]
I used a while loop of the Text::Balanced module or tilly's code to bite off balanced brace chunks and run them through the rest of the code one at a time? This would seem to me to have the memory advantages of the 
while ($line_in_file = <INFILE>)

[download]
line while more suited to my needs. Does that thinking make sense? A lot of little processes instead of one big one? This is extremely helpful advice, thanks again guys!

In reply to Re: Code stalls...possible memory leak? by tshabet
in thread Code stalls...possible memory leak? by tshabet

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.