If you can identify the end of a transaction, and each thread only works on one transaction at a time, you won't have a problem.

Use the thread ID as the hash key, and delete that entry once the transaction is complete and you have done whatever you need to do with the data. That way, you have a nice clean place to start building up info about the thread's next transaction.

The key things:

foreach $file (@files) { open my $FH, '<', $file or die "$file open says $!"; while (<$FH>) { ponder($_); $transactionHash{$threadID}{oldVariableName} = $stuff; delete $transactionHash{$threadID} if $transactionEnded; } }

In reply to Re^2: Interlaced log parser by SuicideJunkie
in thread Interlaced log parser by tzen

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.