You didn't mention this, but if order matters in some way, you would might want two data structures, one to unique the output (a hash) and one to maintain ordering (an array). I don't know if you have seen this with the previous examples, but the header line could get mixed into the file somewhere (randomly, thanks to the hashing algorithm) unless handled separately.
Alternatively, I provide this quick example:
#!/usr/bin/perl
use strict;
use warnings;
my @order; my %data;
while (<DATA>) {
my ($key,$value) = split /\t/, $_, 2;
push @order, $key;
$data{$key} = $value;
}
for my $key (@order) {
printf("%s\t%s", $key, delete $data{$key}) if ($data{$key});
}
__DATA__
COMPUTER DISTRIBUTION_ID STATUS
30F-WKS `1781183799.xxxx1' IC---
30F-WKS `1781183799.xxx11' IC---
ADM34A3F9 `1781183799.41455' IC---
Ivan Heffner
Sr. Software Engineer
WhitePages.com, Inc.
-
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.
|