3 ms·

The default regex functionality is absolutely terrible (maybe this can now be fixed with a PR). You'd write your own cmdlet[1]. A few things are demonstrated in

by zamalek 10y ago

The default regex functionality is absolutely terrible (maybe this can now be fixed with a PR). You'd write your own cmdlet[1]. A few things are demonstrated in the cmdlet: functions that take pipes, functions that return pipes, anonymous functions, actions to perform before processing a pipe and dynamic objects. The Powershell syntax gets ridiculed for being ugly, but it's beautifully expressive. > Can I take the value, convert it to string, make some magic on it and convert it to another object entirely? Get-ChildItem *.js | Get-Content | Select-Regex 'require$"(?<Require>.*?)"$' | Select-Object -ExpandProperty Require In other words: find JS files | read lines | turn regex capture groups into an object (another object entirely) | select a single capture Ultimately, Microsoft provides WMI cmdlets[2]. You'd have strong types from the get-go and wouldn't need resort to this string silliness. [1]: https://gist.github.com/jcdickinson/cee4582448300c0d404bbff1f5669029 https://gist.github.com/jcdickinson/cee4582448300c0d404bbff1... [2]: https://technet.microsoft.com/en-us/library/ee176860.aspx https://technet.microsoft.com/en-us/library/ee176860.aspx

jodrellblank 10y ago
The default regex functionality is absolutely terrible How so?
- zamalek 10y ago
  Replicate the above without using [Regex]:: (i.e. use -matches and $matches). It forces you to radically depart from a typical Powershell mindset and approach.
  - jodrellblank 10y ago
    I'm not certain what you're getting at; -match doesn't handle multiple matches so you can't replicate the above just with it? Yes, that's a bit annoying. You could match line by line: gci *.js | foreach { gc $_ | foreach { if ($_ -match ..) { $Matches... which is ugly, but doesn't use [regex]::Matches. But you can do: sls 'require$"(.*?)"$' *.js | select { $_.Matches.groups[1] } or other variants of Select-String, depending on exactly what data you want, without departing into the .Net Framework too far.

by zamalek 10y ago

jodrellblank 10y ago

The default regex functionality is absolutely terrible How so?

zamalek 10y ago
Replicate the above without using [Regex]:: (i.e. use -matches and $matches). It forces you to radically depart from a typical Powershell mindset and approach.
- jodrellblank 10y ago
  I'm not certain what you're getting at; -match doesn't handle multiple matches so you can't replicate the above just with it? Yes, that's a bit annoying. You could match line by line: gci *.js | foreach { gc $_ | foreach { if ($_ -match ..) { $Matches... which is ugly, but doesn't use [regex]::Matches. But you can do: sls 'require$"(.*?)"$' *.js | select { $_.Matches.groups[1] } or other variants of Select-String, depending on exactly what data you want, without departing into the .Net Framework too far.