I agree with hawtin about making a hash with keys based on the source and destination (reversed for replies). But what you need to gather the messages together is a hash of arrays. That will also preserve the sequence within each exchange, since I assume the log is in time order. (It will not preserve the overall sequence, but that could be another sort after you have them grouped). Here is my implementation:
use strict; my %calls; while (<>) { my $line = $_; my ($num, $source, $dest, $type) = split (/\s+/,$line,5); my $key; if ($type eq "GetReply") { $key = $dest . ":" . $source; } else { $key = $source . ":" . $dest; } push @{$calls{$key}}, $line; } foreach my $k (sort keys %calls) { print join('', @{$calls{$k}}),"\n\n"; }

In reply to Re: Need sorting help by tall_man
in thread Need sorting help by Anonymous Monk

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.