{"id":2272,"date":"2009-04-04T19:54:00","date_gmt":"2009-04-04T19:54:00","guid":{"rendered":"https:\/\/ikaisays.com\/?p=2272"},"modified":"2021-04-20T19:55:42","modified_gmt":"2021-04-20T19:55:42","slug":"using-pattern-matching-with-regular-expressions-in-scala","status":"publish","type":"post","link":"https:\/\/ikaisays.com\/2009\/04\/04\/using-pattern-matching-with-regular-expressions-in-scala\/","title":{"rendered":"Using pattern matching with regular expressions in Scala"},"content":{"rendered":"\n

I\u2019ve been trying to use Scala more and more so I can gain some experience and exposure to it. A couple of weeks ago, I wrote a Scala log parser for Ruby on Rails<\/a>. It is terribly newbie-ish \u2013 the classes are mutable and it\u2019s disorganized. It\u2019s a mess. Jorge Ortiz from the Scala mailing list was kind enough to rewrite it in a more Scala style<\/a>. It completely blew my mind how terse Scala can become when written correctly.<\/p>\n\n\n\n

It bothered me, however, dealing with regular expressions the way that I did. The Java interface is pretty clumsy and nowhere near as clean as regular expression pattern extraction in Perl or Ruby.<\/p>\n\n\n\n

As it turns out, it\u2019s surprisingly easy to extract text using Regular Expressions in Scala. Throw away Pattern.compile! Check out this hotness below:<\/p>\n\n\n\n

First, let\u2019s import Scala\u2019s regex package:<\/p>\n\n\n\n

import scala.util.matching.Regex<\/code><\/p>\n\n\n\n

Now we declare a regular expression to match against. We can do this one of two ways:<\/p>\n\n\n\n

val LogEntry = new Regex(\"\"\"Completed in (\\d+)ms \\(View: (\\d+), DB: (\\d+)\\) \\| (\\d+) OK \\[http:\/\/app.domain.com(.*)\\?.*\"\"\")<\/code><\/p>\n\n\n\n

I use triple quotes here to signify that I am creating a raw string. A raw string means that I do not need to escape characters like the \\ character. If I didn\u2019t do this, I\u2019d be forced to use strings like \u201c\\\\d+\u201d. Believe it or not, that extra slash throws me off. Just goes to show that I have written way too many parsers.<\/p>\n\n\n\n

Alternatively, I can declare a new Regex by doing this:<\/p>\n\n\n\n

val LogEntry = \"\"\"Completed in (\\d+)ms \\(View: (\\d+), DB: (\\d+)\\) \\| (\\d+) OK \\[http:\/\/app.domain.com(.*)\\?.*\"\"\".r<\/code><\/p>\n\n\n\n

Strings have a method called \u201cr\u201d, which will convert it to a Regex object. I\u2019m not sold on this syntax at the moment, since it doesn\u2019t play well with eyeball scans, but I\u2019m putting it here for those folks that absolutely need to save characters.<\/p>\n\n\n\n

There\u2019s nothing really special here yet. The next step is REALLY cool:<\/p>\n\n\n\n

val line = \"Completed in 100ms (View: 25, DB: 75) | 200 OK [http:\/\/app.domain.com?params=here]\"<\/code><\/p>\n\n\n\n

scala> val LogEntry(totalTime, viewTime, dbTime, responseCode, uri) = line
totalTime: String = 100
viewTime: String = 25
dbTime: String = 75
responseCode: String = 200
uri: String =<\/code><\/p>\n\n\n\n

The local variables totalTime, viewTime, dbTime, responseCode and uri are now bound to the values we want to extract from the original line! The regular expression value defines an unapplySeq method. I\u2019m not quite good enough at Scala to tell you in any definite terms what that means, except that you can use the code in a pattern match:<\/p>\n\n\n\n

line match {
case LogEntry(totalTime, viewTime, dbTime, responseCode, uri) => {
\/* Process the data *\/
\/\/ do something with totalTime.toInt
\/\/ do something with viewTime.toInt
\/\/ etc ...
}
case _ => \/\/ Do nothing
}<\/code><\/p>\n\n\n\n

Because you can use a pattern match, and patterns will be be matched in the order of definition, this means that you can create several regular expressions representing lines you want to extract, then process them easily in using pattern matching.<\/p>\n\n\n\n

Pretty powerful stuff. What would really make my day would be if someone knew how I could extract the values totalTime, viewTime, and dbTime as integers and not have to do a conversion \u2013 I\u2019m already matching with \\d+. Ideas?<\/p>\n","protected":false},"excerpt":{"rendered":"

I\u2019ve been trying to use Scala more and more so I can gain some experience and exposure to it. A couple of weeks ago, I … Read More<\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_generate-full-width-content":""},"categories":[1],"tags":[],"_links":{"self":[{"href":"https:\/\/ikaisays.com\/wp-json\/wp\/v2\/posts\/2272"}],"collection":[{"href":"https:\/\/ikaisays.com\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/ikaisays.com\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/ikaisays.com\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/ikaisays.com\/wp-json\/wp\/v2\/comments?post=2272"}],"version-history":[{"count":1,"href":"https:\/\/ikaisays.com\/wp-json\/wp\/v2\/posts\/2272\/revisions"}],"predecessor-version":[{"id":2273,"href":"https:\/\/ikaisays.com\/wp-json\/wp\/v2\/posts\/2272\/revisions\/2273"}],"wp:attachment":[{"href":"https:\/\/ikaisays.com\/wp-json\/wp\/v2\/media?parent=2272"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/ikaisays.com\/wp-json\/wp\/v2\/categories?post=2272"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/ikaisays.com\/wp-json\/wp\/v2\/tags?post=2272"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}