Re^2: Store and print multiple strings

Hi, I'm capturing the string using (.\d+\.\d+) with the . matching the ~ since that is only present if the values are 0.00. If they were 51.11 for example, there would be no ~ but would still match as there's spaces after Util before the actual digit. Might be a better way to do that?

My values are just printed to screen and are held in $text:

my $text = $host->cmd("monitor lag $lag_traffic interval 3 repeat 3 ra
+te | match Totals post-lines 1");
[download]

$lag_traffic is just derived from another input that is held in @lag_id:

my $lags   = $host->cmd("show lag description");
  my @lag_id = ( $lags =~ m/(\d+)\Se\S/g );
[download]

For a guess, you're pretty spot on. Essentially what I want is to have the following displayed:

LAG ID 200:
1 - Input - x Output - x
2 - Input - x Output - x
3 - Input - x Output - x
LAG ID 199:
1 - Input - x Output - x
2 - Input - x Output - x
3 - Input - x Output - x

Your recommendation solves why it was just counting the contents, so thank you. Given I know the first value in the text is always input and the second is always output, would it be easier to split them up before or after putting them in the key?

Comment on Re^2: Store and print multiple strings Select or Download Code

Replies are listed 'Best First'.
Re^3: Store and print multiple strings by AnomalousMonk (Archbishop) on Mar 12, 2018 at 15:02 UTC
... the ~ ... is only present if the values are 0.00. Since you seem to want to capture only a `~` (tilde), if present, and no other character (including, in one case, a `-` (negative sign) in the example below), I would use: `c:\@Work\Perl\monks>perl -wMstrict -MData::Dump -le "my $text = 'foo ~0.00 bar 1.0 fee 0.2 baz 0.03 boff -0.09 zot 10.09'; my @lag_util = $text =~ m{ ~? \d+ [.] \d+ }xmsg; dd \@lag_util; " ["~0.00", "1.0", "0.2", "0.03", "0.09", "10.09"]` [download] Give a man a fish: `<%-{-{-{-<`	[reply] [d/l] [select]
Re^3: Store and print multiple strings by roboticus (Chancellor) on Mar 12, 2018 at 15:36 UTC
bartrad: Sorry about that, I didn't read your code carefully enough, and managed to overlook the initial '.' in your regex, and managed to flub my initial response. If you're always getting six values and you want to format them as you describe, I don't really see any reason to prefer splitting them up before putting them in the hash versus splitting them up afterwards when you're printing your report. Generally, I try to let the problem I'm solving guide my choices on building the data structure. If you're doing further processing between the "acquire the data" step and the "report the data" step, then that further processing might be simpler if the data were stored one way vs. storing it the other way. If you don't have an intermediate step yet, but suspect you may in the future, then you might want to put the data in a format suitable for the expected processing if it's no more difficult one way or the other. If there's any extra effort required to put the data in that form and you're not sure you'll use the script again, then you might just put a nice comment in the form of: `# TODO: if we need to jibber the frobnitz, we might want to reform +at the data like # $lag_load{$lag_traffic} = [ [ $inVal1, $outVal1 ], ... ]; # or # $lag_load{$lag_traffic} = [ { in=>$inVal1, out=>$outVal1 }, ... +]; # be sure to update the zig_zag_report subroutine accordingly!` [download] to prompt the future you, if/when the need arises. That way, you don't have to spend the effort unless necessary. Since it's just a comment to give you a little context when you revisit the code, it need not be syntactically perfect--you're just wanting to pass on some ideas to your future self while the code is fresh in your mind. ...roboticus When your only tool is a hammer, all problems look like your thumb.	[reply] [d/l]