A rather strange looking solution, but with an approach that can be extended to many such situations: (and no I don't think this is the "best" solution).
#!/usr/bin/perl
use strict;
use warnings;
my $line;
while ( defined ($line = <DATA>))
{
if ($line =~ /^name/)
{
$line = process_record ($line);
redo if defined $line; # another name line
}
}
sub process_record
{
my $line = shift;
(my $name) = $line =~ /^name\s+(\w+)/;
my %devices;
while (defined ($line = <DATA>) and $line !~ /^name/)
{
if ( (my $device) = $line =~ /^device\s+(\w+\s+\w+)/)
{
$device =~ s/(\w+)\s+(\w+)/$1 $2/;
$devices{$device}=1;
}
}
print "$name:\n";
print " device $_\n" foreach keys %devices;
return $line;
}
=PRINTS:
Brian:
device ipad 2001
Andrew:
device ipad 2009
ryan:
device ipad 2005
device cell 2009
=cut
__DATA__
socks something
name Brian
shirt yellow
socks black
device ipad 2001
device ipad 2001
device ipad 2001
tag no
tag 0
name Andrew
shirt orange
socks black
device ipad 2009
tag no
tag 0
name ryan
shirt blue
socks black
device ipad 2005
device cell 2009
tag yes
tag 1
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|