Unless I'm overlooking something, you're overcomplicating it
use strict;
use warnings;
my %clean_data;
chomp (my @data_array = <DATA>);
for my $data ( @data_array)
{
my ($server, @info) = split (/,/,$data);
$data = \@info;
push @{$clean_data{$server}}, $data;
}
#use Data::Dumper;die Dumper\%clean_data;
print
$_,
$/,
map { "\t@$_$/"} @{$clean_data{$_}}
for
sort
keys %clean_data;
__DATA__
server_A, Perl, UK
server_A, Word, UK
server_A, Outlook, UK
server_A, Excel, UK
server_B, Reuters, NL
server_B, TradeXL, NL
server_B, Thompsons, NL
server_B, Bloomberg, NL
server_B, Tibco, NL
server_c, BasketLink, USA
server_c, Evolution, USA
server_c, Lotus, USA
server_c, TIB, USA
server_A, Python, UK
MJD says "you can't just make shit up and expect the computer to know what you mean, retardo!" |
I run a Win32 PPM repository for perl 5.6.x and 5.8.x -- I take requests (README). |
** The third rule of perl club is a statement of fact: pod is sexy. |
-
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.