I wonder if you would do better with two hashes rather than two arrays. You could join your array with newlines and open a filehandle against a reference to the resultant scalar. You could then read it in paragraph mode one record at a time and use splits in maps to populate the hashes.
$ perl -Mstrict -Mwarnings -MData::Dumper -E '
my @array = (
q{CPU Temp = 30},
q{GFX Temp = 45},
q{RAM Temp = 40},
q{},
q{CPU Status = OK},
q{GFX Status = OK},
q{RAM Status = OK},
);
open my $inFH, q{<}, \ do { join qq{\n}, @array } or die $!;
my( %temps, %stats );
{
local $/ = q{};
%temps =
map { split m{\s+=\s+} }
map { split m{\n} }
scalar <$inFH>;
%stats =
map { split m{\s+=\s+} }
map { split m{\n} }
scalar <$inFH>;
}
print Data::Dumper
->new( [ \ %temps, \ %stats ], [ qw{ *temps *stats } ] )
->Sortkeys( 1 )
->Dumpxs();'
%temps = (
'CPU Temp' => '30',
'GFX Temp' => '45',
'RAM Temp' => '40'
);
%stats = (
'CPU Status' => 'OK',
'GFX Status' => 'OK',
'RAM Status' => 'OK'
);
$
I hope this is helpful.
-
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.