I would put the records into groups, and then loop through the groups, each as a single entity to decide if it needs a header record. For you, the trick is preserving order so we can build the header record using data about the previous group. Luckily there's
Tie::IxHash:
use Tie::IxHash;
tie my %group, Tie::IxHash;
## group them by ID, preserving the order seen
for (@records) {
my $id = $_->{ID};
push @{ $group{$id} }, $_;
}
## put special header at beginning of groups larger than 1
my $last_id;
while (my ($curr_id, $records) = each %group) {
unshift @$records, { ... } if @$records > 1;
$last_id = $curr_id;
}
## flatten everything out
my @complete_list = map @$_, values %group;
Notice when you put the header record onto the beginning of the group, you can use
$last_id,
$curr_id,
$records, and even
$group{$last_id} to generate it.
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.