A little closer to production code by opening a "file" and checking for unexpected data:
use strict;
use warnings;
use Data::Dumper;
my $testData = <<DATA;
>James
>40
>James
>35
>James
>26
>James
>15
DATA
open my $fin, '<', \$testData or die "Can't open file: $!\n";
my %people;
my $lastPerson;
while (defined (my $line = <$fin>)) {
chomp $line;
if ($line =~ /^>(\d+)$/) {
die "Unexpected data order: '$line'\n" if !defined $lastPerson
+;
push @{$people{$lastPerson}}, $1;
next;
}
if ($line =~ /^>(\w+)$/) {
$lastPerson = $1;
next;
}
warn "Don't know how to process '$line'\n";
}
print Dumper(\%people);
Prints:
$VAR1 = {
'James' => [
'40',
'35',
'26',
'15'
]
};
Optimising for fewest key strokes only makes sense transmitting to Pluto or beyond
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.