Re^3: Extracting non-consecutive but related items from an array.

Yes, I think its $server too....Thanks guys.

But, Can I have simple breakup of this code?

print
    $_,
    $/,
    map { "\t@$_$/"} @{$clean_data{$_}}
    for
        sort
            keys %clean_data;
[download]

And, why did we have to reference \ @apps_info? couldn't we use it without referencing?

Blackadder

Comment on Re^3: Extracting non-consecutive but related items from an array. Download Code

Replies are listed 'Best First'.
Re^4: Extracting non-consecutive but related items from an array. by robartes (Priest) on Jun 15, 2005 at 09:46 UTC
And, why did we have to reference \ @apps_info? couldn't we use it without referencing? No particular reason, it's just that that's the way I like doing things. This way, the information contained in one line in the input file stays readily identifiable (it's one element of the array for that server), whereas pushing on the first level array would result in a flat list. But it's just a preference thing, I guess. CU Robartes-	[reply]
simple breakup of this code by Anonymous Monk on Jun 15, 2005 at 13:43 UTC
$/ is the The input record separator, newline by default (see the perlop man page; type perldoc perlop and find it). The code you posted could be re-written like this: foreach my $key (sort keys %clean_data) { print $key, $/; foreach my $data (@{$clean_data{$key}}) { # the hash value $clean_data{$key} is an array reference # wrapping it in @{} gives us the array it references. # this array contains array references, # so @$data gives us an array print "\t", @$data, $/; } } - Dotan	[reply]