{"id":17203,"date":"2009-08-06T10:00:00","date_gmt":"2009-08-06T10:00:00","guid":{"rendered":"https:\/\/blogs.msdn.microsoft.com\/oldnewthing\/2009\/08\/06\/the-great-thing-about-regular-expression-engines-is-that-there-are-so-many-to-choose-from\/"},"modified":"2009-08-06T10:00:00","modified_gmt":"2009-08-06T10:00:00","slug":"the-great-thing-about-regular-expression-engines-is-that-there-are-so-many-to-choose-from","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/oldnewthing\/20090806-00\/?p=17203\/","title":{"rendered":"The great thing about regular expression engines is that there are so many to choose from"},"content":{"rendered":"

Back in the days before perl ruled the earth, regular expressions were one of those weird niche features, one of those things that everybody reimplements when they need it. If you look at the old unix tools, you’ll see that even then, there were three different regular expression engines with different syntax. You had grep<\/code>, egrep<\/code>, and vi<\/code>. Probably more.\n The grep<\/code> regular expression language supported character classes, the dot wildcard, the asterisk operator, the start and end anchors, and grouping. No plus operator, no question mark, no alternation, no repetition counts. The egrep<\/code> program added support for plus, question mark, and alternation. Meanwhile, somebody went back and added repetition counts to grep<\/code> but didn’t add them to vi<\/code>; somebody else added the \\<<\/code> and \\><\/code> metacharacters to vi<\/code> but didn’t add them to sed<\/code>. POSIX added repetition counts to awk<\/code> but changed the notation from \\{n,m\\}<\/code> to {n,m}<\/code>. And so on.\n No two programs use the same regular expression language, but they overlap sufficiently that you can often get by with the common subset and not have to worry about which particular flavor you’re up against.<\/p>\n

Until you wander into the places where they differ. <\/p>\n

\n

From<\/b>: John Jones
Subject<\/b>: Problem with regular expression <\/p>\n

I’m trying to write a regular expression to match blah blah blah. <\/p>\n<\/blockquote>\n

\n

From<\/b>: Jane Smith
Subject<\/b>: RE: Problem with regular expression <\/p>\n

I think this will match what you want: ^Z@1&*B*!34 <\/p>\n<\/blockquote>\n

I just ran my hand randomly over the keyboard to generate that fake regular expression. The scary thing is, at first glance, it is not obviously not<\/i> a regular expression! <\/p>\n

\n

From<\/b>: Chris Brown
Subject<\/b>: RE: Problem with regular expression <\/p>\n

Try $)(#$C)*# <\/p>\n<\/blockquote>\n

\n

From<\/b>: John Smith
Subject<\/b>: RE: Problem with regular expression <\/p>\n

Thanks, everybody, for your suggestions, but I can’t get any of them to work. For example, I can’t get any of them to match against this string: blah blah blah blah. <\/p>\n<\/blockquote>\n

At this point, people chimed in with other suggestions, confirming that John doubled the backslashes, that sort of thing. John posted his test program, and then the reason was obvious. <\/p>\n

\n

From<\/b>: Jane Smith
Subject<\/b>: RE: Problem with regular expression <\/p>\n

Oh, you’re using CAtlRegExp<\/code><\/a>. In that class, \\w<\/code> doesn’t match a single character; it matches an entire word<\/a>. You want to use \\a<\/code> instead. <\/p>\n<\/blockquote>\n","protected":false},"excerpt":{"rendered":"

Back in the days before perl ruled the earth, regular expressions were one of those weird niche features, one of those things that everybody reimplements when they need it. If you look at the old unix tools, you’ll see that even then, there were three different regular expression engines with different syntax. You had grep, […]<\/p>\n","protected":false},"author":1069,"featured_media":111744,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1],"tags":[25],"class_list":["post-17203","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-oldnewthing","tag-code"],"acf":[],"blog_post_summary":"

Back in the days before perl ruled the earth, regular expressions were one of those weird niche features, one of those things that everybody reimplements when they need it. If you look at the old unix tools, you’ll see that even then, there were three different regular expression engines with different syntax. You had grep, […]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/posts\/17203","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/users\/1069"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/comments?post=17203"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/posts\/17203\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/media\/111744"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/media?parent=17203"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/categories?post=17203"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/tags?post=17203"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}