I've been working on something the last week that brought me back into sometimes frightening world of regular expressions. But as the saying goes, we only fear what we don't understand. So a little knowledge can be a wonderful thing. In this particular situation I was looking for a regular expression to determine if a number fell within a certain range. I know I can use an operator statement in a compound expression like ($x -gt 0) -AND ($x -le 10) but I that would require additional parsing. Plus I decided this was an opportunity to whittle away at my regular expression deficiencies. Now I know how to tell using regular expressions if a string contains a number between say 1 and 10. Here's how.
\n<\/p>\n
The first step is to remember that regular expressions are all about patterns. We're not looking at values. When constructing a number pattern you have to break it down. Let's start simply and see if the number in my text is between 0 and 9. My regular expression uses a range: [0-9].
\n[cc lang=\"PowerShell\"]
\nPS S:\\> $x=4
\nPS S:\\> $x -match \"[0-9]\"
\nTrue
\nPS S:\\> $x=3
\nPS S:\\> $x -match \"[0-9]\"
\nTrue
\nPS S:\\> $x=-1
\nPS S:\\> $x -match \"[0-9]\"
\nTrue
\nPS S:\\> $x=11
\nPS S:\\> $x -match \"[0-9]\"
\nTrue
\n[\/cc]
\nWe're starting simple. As you can see I get the results I expected until I hit numbers like -1 and 11. Those still return True but that's not what I want. That's because regular expression patterns \"float\". Take 11. My expression says look for anything that is between 0 and 9. Looking at $matches from the last comparison I can see I in fact matched on 1.
\n[cc lang=\"PowerShell\"]
\nPS S:\\> $matches<\/p>\n
Name Value
\n---- -----
\n0 1
\n[\/cc]
\nThe solution is to anchor my pattern.
\n[cc lang=\"PowerShell\"]
\nPS S:\\> $x -match \"^[0-9]$\"
\nFalse
\n[\/cc]
\nWith $x still 11 now I get the result I expected because my pattern says look for something that starts (^) and ends ($) with a number between 0 and 9.
\n[cc lang=\"PowerShell\"]
\nPS S:\\> $x=6
\nPS S:\\> $x -match \"^[0-9]$\"
\nTrue
\n[\/cc]
\nA 0-9 range is rarely sufficient. More than likely I need a greater range, say up to 25. This is where it gets interesting. You need to create a pattern for each digit. We'll focus on validating 20-25. I need a pattern for the first part, a 2 and something for second part to cover 0-5. I'll end up with a more complex regular expression: \"^[2][0-5]$\". Here's a quick way to test.
\n[cc lang=\"PowerShell\"]
\nPS S:\\> (19..30) -match \"^[2][0-5]$\"
\n20
\n21
\n22
\n23
\n24
\n25
\n[\/cc]
\nI can see that only numbers 20-25 are returned. To validate numbers 1 to 25 I need to combine my expressions.
\n[cc lang=\"PowerShell\"]
\nPS S:\\> (1..30) -match \"^([1-9]|[1][0-9]|[2][0-5])$\" | measure-object<\/p>\n
Count : 25
\nAverage :
\nSum :
\nMaximum :
\nMinimum :
\nProperty :
\n[\/cc]
\nRather than list out all the matching numbers which you can so, I simply measured the result so you could see I in fact got 25 matches. My expression is slightly more complicated. The first part [1-9] matches 1-9. The second part, [1][0-9], after the OR (|) gets all numbers that start with 1 and end with 0-9. In other words, 10-19. The last part, [2][0-5], covers numbers 20-25. Do you see it? Ready for one more? Here's an expression that validates 1-50.
\n[cc lang=\"PowerShell\"]
\nPS S:\\> (1..100) -match \"^([1-9]|[1-4][0-9]|[5][0])$\" | measure-object<\/p>\n
Count : 50
\nAverage :
\nSum :
\nMaximum :
\nMinimum :
\nProperty :
\n[\/cc]
\nThe second part matches all numbers that start with 1-4 and end with 0-9 which covers 10-49. The last part finds numbers that start with 5 and end in 0. Taking this a step further I can now beginning writing PowerShell expressions like these:
\n[cc lang=\"PowerShell\"]
\nPS S:\\> \"File45\" -match \"^file([1-9]|[1-4][0-9]|[5][0])$\"
\nTrue
\nPS S:\\> \"File95\" -match \"^file([1-9]|[1-4][0-9]|[5][0])$\"
\nFalse
\nPS S:\\> \"File5\" -match \"^file([1-9]|[1-4][0-9]|[5][0])$\"
\nTrue
\nPS S:\\> \"File15\" -match \"^file([1-9]|[1-4][0-9]|[5][0])$\"
\nTrue
\n[\/cc]
\nTo write a pattern for a 3 digit number take what I've shown you here and simply extend it for the third digit. I'll leave that exercise to you.<\/p>\n","protected":false},"excerpt":{"rendered":"
I’ve been working on something the last week that brought me back into sometimes frightening world of regular expressions. But as the saying goes, we only fear what we don’t understand. So a little knowledge can be a wonderful thing. In this particular situation I was looking for a regular expression to determine if a…<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":false,"jetpack_social_options":{"image_generator_settings":{"template":"highway","default_image_id":0,"font":"","enabled":false},"version":2}},"categories":[4,8],"tags":[534,250],"class_list":["post-1095","post","type-post","status-publish","format-standard","hentry","category-powershell","category-scripting","tag-powershell","tag-regular-expressions"],"yoast_head":"\n