Skip to main content

Groovy closures

Java does not have closures, but till sometime back it was a highly debated topic on various Java forums. Groovy is a language which compiles to Java bytecode and does have closures.

Closures are very prominent in many programming languages, such as Groovy, Python, Ruby, Javascript, and probably many more.

So what are closures? A closure is a block of code which can be passed to a function. Closures in Groovy are normal objects, which do not have any visible state.

Closures are most often used in iteration logic and resource handling.

Whenever we iterate across a collection, we normally do so to perform some logic on all or some members of the collection. Closures make it easy to represent that logic in a very concise and readable way.

Closures can also be used for resource handling. Very often we open a file resource do something with the file (read from it, write to it, or both), and then close the file. The first and last parts, that is opening and closing the file are really plumbing code. The interesting part is what we do with it. Using closures it is possible to create objects which will take care of the plumbing and will perform some operations on the file, such that the code which represents the operations are given to it in a closure.

Here is an example. Let's assume we have a list of Toy objects, where each toy object has a color which can be accessed with the getColor() method. I want all the blue toys and my sister wants all the pink toys.

Here is code to get toys for me using regular Java syntax:

Color myFavColor = Color.BLUE;
List toysIWant = new ArrayList()
Iterator iter = toys.iterator();
while(iter.hasNext()) {
Toy toy = (Toy)iter.next();
if(toy.getColor().equals(myFavColor)) {
toysIWant.add(toy);
}
}


Here is code to get toys for my sister using closures:

def mySistersFavColor = Color.PINK
def toysMySisterWants = toys.grep() {
it.getColor() == mySistersFavColor
}


What really happened in the second code snippet was, the list object has a grep method which takes a closure. It calls that closure for every item in the list and passes that item to the closure as the variable 'it'. If the expression in the closure evaluates to true, then the item is added to an internal list. This list is returned to the caller when grep returns.

You might be thinking that this can be done in Java using anonymous inner classes. That is partially right. But there are two very important differences. Anonymous inner classes cannot refer to non static local variables in the scope they are declared in, which means they could not have referred to the variables 'myFavCOlor', and 'mySistersFavColor'. Another difference is that anonymous inner classes are very verbose. This may not seem important, but many people have said that it is something that makes anonymous inner classes unusable.

Resources:

Comments

Popular posts from this blog

Five Reasons Why Your Product Needs an Awesome User Guide

Photo Credit: Peter Merholz ( Creative Commons 2.0 SA License ) A user guide is essentially a book-length document containing instructions for installing, using or troubleshooting a hardware or software product. A user guide can be very brief - for example, only 10 or 20 pages or it can be a full-length book of 200 pages or more. -- prismnet.com As engineers, we give a lot of importance to product design, architecture, code quality, and UX. However, when it comes to the user manual, we often only manage to pay lip service. This is not good. A usable manual is as important as usable software because it is the first line of help for the user and the first line of customer service for the organization. Any organization that prides itself on great customer service must have an awesome user manual for the product. In the spirit of listicles - here are at least five reasons why you should have an awesome user manual! Enhance User Satisfaction In my fourteen years as a

Inheritance vs. composition depending on how much is same and how much differs

I am reading the excellent Django book right now. In the 4th chapter on Django templates , there is an example of includes and inheritance in Django templates. Without going into details about Django templates, the include is very similar to composition where we can include the text of another template for evaluation. Inheritance in Django templates works in a way similar to object inheritance. Django templates can specify certain blocks which can be redefined in subtemplates. The subtemplates use the rest of the parent template as is. Now we have all learned that inheritance is used when we have a is-a relationship between classes, and composition is used when we have a contains-a relationship. This is absolutely right, but while reading about Django templates, I just realized another pattern in these relationships. This is really simple and perhaps many of you may have already have had this insight... We use inheritance when we want to allow reuse of the bulk of one object in other

Planning a User Guide - Part 3/5 - Co-ordinate the Team

Photo by  Helloquence  on  Unsplash This is the third post in a series of five posts on how to plan a user guide. In the first post , I wrote about how to conduct an audience analysis and the second post discussed how to define the overall scope of the manual. Once the overall scope of the user guide is defined, the next step is to coordinate the team that will work on creating the manual. A typical team will consist of the following roles. Many of these roles will be fulfilled by freelancers since they are one-off or intermittent work engagements. At the end of the article, I have provided a list of websites where you can find good freelancers. Creative Artist You'll need to work with a creative artist to design the cover page and any other images for the user guide. Most small to mid-sized companies don't have a dedicated creative artist on their rolls. But that's not a problem. There are several freelancing websites where you can work with great creative ar