Join the DZone community and get the full member experience.
Join For FreeDownload Microservices for Java Developers: A hands-on introduction to frameworks and containers. Brought to you in partnership with Red Hat.
In a recent
post, this blog examined the meaning of Closures' delegates and how they could be changed. This post will show how the ability to set the closure's delegate allows the language to become quite expressive where other languages remain cumbersome and verbose. For the purpose of example (
and some fun) consider there is a groovy object
drico, which represents the legendary Irish rugby player,
Brian O'Driscoll
In case you don't know, Brian O'Driscoll is the best Rugby player to ever come from Ireland. He could tackle, break, off load, ruck, jackal, kick you name it. An exceptional skilful athlete and widely regarded as one of the greatest players the game has ever seen. In case, you don't know what Rugby is think American Football with no helmets, timeouts and a slightly longer shaped oval ball. It is basically superior in every regard. Anyway, so we have the
drico object in our Groovy code suppose and we want to invoke a bunch of methods on it. We could find ourselves doing:
Wow, that's a lot methods being invoked on Drico. There must be some Groovy trick we could do to lessen the text here? Remember, it is generally better to be coding than typing
Well we could put all the methods we want to invoke on Drico into a Closure and then set that Closure's delegate to Drico.
Not bad. We have removed all the
Using this approach means we have still removed all the
RugbyPlayer drico = new RugbyPlayer(); ... drico.youWereAmazing(); drico.seriouslyYouWereAmazing(); drico.sayTotsAmazeBalls(); drico.howManyTriesDidYouScore(); drico.youreTheBest(); ...
Well we could put all the methods we want to invoke on Drico into a Closure and then set that Closure's delegate to Drico.
RugbyPlayer drico = new RugbyPlayer();
...
def dricoClosure = {
youWereAmazing();
seriouslyYouWereAmazing();
sayTotsAmazeBalls();
howManyTriesDidYouScore();
youreTheBest();
...
}
dricoClosure.delegate = drico
dricoClosure();
drico., and just gone straight to the method invocations but we have also added some code setting up the closure delegate. So one step forward, one step back. We can get rid of the
one step backby using Groovy's
with method. The
with method is applicable to any Groovy object and accepts one closure. The delegate of the closure is the object
with is being invoked on. This means we can do this:
RugbyPlayer drico = new RugbyPlayer();
drico.with {
youWereAmazing();
seriouslyYouWereAmazing();
sayTotsAmazeBalls();
howManyTriesDidYouScore();
youreTheBest();
...
}
drico. and gone straight to the method invocations. It also means we don't need to set the closure's delegate and we don't need to explicitly invoke the closure. The result is we have code with a much better signal to noise ratio and which is far more expressive. Until the next time take care of yourselves.
Download Building Reactive Microservices in Java: Asynchronous and Event-Based Application Design. Brought to you in partnership with Red Hat.
Like This Article? Read More From DZone
Topics:
Published at DZone with permission of Alex Staveley , DZone MVB. See the original article here.
Opinions expressed by DZone contributors are their own.
{{ parent.title || parent.header.title}}
{{ parent.tldr }}
{{ parent.linkDescription }}
{{ parent.urlSource.name }}