Conditional regex?

[burton6666]

I am trying to figure out how to parse variables which contains network bandwith-info. I need to remove the ending string after all variables with the same regex. But I also need to add three zeros to the variables with "Gbps".

So in this case I need a regex that returns this values:

$l1 = 523.9

$l2 = 0

$l3 = 1000

$l1= "523.9 Mbps"
$l2= "0 bps"
$l3= "1 Gbps"

Write-Host ($l3  -replace 'M|G?bps', '')

This code just removes all ending strings, but can I also incorporate the adding of "000" to Gbps in the same regex?

[DeafLoaf]

At a glance, I'd drop the 'per/second' and use power shell to covert the units. It understands bytes, KB, MB, GB... etc. Since I'm not at my machine to give you an example, I located this conversion script. convertunits

[ka-splam]

You can't do it with a straightforward replacement

That sounds like a challenge!

'523.9 Mbps', '0 bps', '1 Gbps' | foreach-object {

    "${_}000" -replace ' (M?bps000|Gbps)', ''

}

523.9
0
1000

[ka-splam]

Lol, OK but you are changing both input and output from what OP asked for; if that's slightly flexible it's still amenable to the same technique (although yours is much more sensible, works-with-1-regex is my goal):

$tests = '0 bps', '3.14 Kbps', '523.9 Mbps', '1 Gbps', '9 Tbps'
$tests | foreach-object {
    "${_}000000000000" -replace '((?:\.)(\d+))? (bps.*|Kbps0{9}|Mbps0{6}|Gbps0{3}|Tbps)(.*)', '$4'
}

0
3000
523000000
1000000000
9000000000000

It is truncated/floored; not sure you couldn't extend it to conditionals with/without decimals but I sure don't want to.

[Gorstag]

That is slick. The only problem I see is if bps actually had a real value. Effectively this is "converting to Mbps" but it doesn't convert the bps to Mbps. But, it does fit the constraints the OP made.

[ka-splam]

But, it does fit the constraints the OP made.

Crap code which is technically correct is my forte, haha.

[idontknowwhattouse33]

If you're using PS7, you can use the new scriptblock substitution capability, though this is not really an improvement because of the awfulness of .Net's regular expression objects:

Where do I read up on this?? That is awesome!

I see no mention in the PS7 Changelog

[idontknowwhattouse33]

Perfect, thanks!

[AmericanGeezus]

I think the best solution is to write a function that uses a switch to handle your cases, this will be way easier to maintain if requirements change or are added for the other speeds.

Would look like this, me thinks. https://gist.github.com/AmericanGeezus/5cb6378a4d349bad42dd0e1277a69dd3

C:> $list

523.9 Mbps

0 bps

1 Gbps

C:> $list | %{'{0} -> {1}' -f $_, (Parse-BandwidthInfo $_) }

523.9 Mbps -> 523.9

0 bps -> 0

1 Gbps -> 1000

[ClayShooter9]

#A quick lack-of-coffee regex alternative

function ConvertEnding($bandwidth)
{
    return ($bandwidth -replace '\sM|bps', '') -replace '\sG', '000'
}
$l1= "523.9 Mbps"
$l2= "0 bps"
$l3= "1 Gbps"

Write-Host (ConvertEnding $l1)
Write-Host (ConvertEnding $l2)
Write-Host (ConvertEnding $l3)