Skip to main content

String handling in Groovy

This blog post shows through a simple example, how to manage strings in Groovy. Here are a few things which are different in Groovy strings:
  • Groovy strings can be enclosed within

    • single quotes: 'this is a string'

    • double quotes: "this is a string"

    • triple (single or double) quotes: '''this is a string''' and """so is this"""

  • Groovy has something called GStrings which uses replacement variables
  • Groovy makes it easier to use strings in regular expressions

  • The == operator in Groovy actually invokes the equals() method

  • Groovy overloads the +, -, and * operators in Strings

With these concepts in mind the example below should be self explanatory. Try running this example yourself and see the output. After that change the source and see how it affects the output.

//Groovy allows single quoted strings
def string1 = 'hello world'
println string1

//Groovy allows double quoted strings (GStrings have to be double quoted)
def string2 = "Hello World"
println string2

//Groovy has something called GStrings which are regular strings which can
//contain replacement variables. These can be variables, or expressions.
//GStrings have to be double quoted
def gstring = "${string2} is so outdated now!"
println gstring

//GStrings can contain expressions and they are a separate datatype in Java
println "2 + 2 = ${2+2}"
println "GString is a separate datatype in Groovy: ${gstring.class.getName()}"

//multiline strings should be enclosed within triple (single or double) quotes
//Notice how the newline character and leading spaces in lines 2 and 3 are taken
//as part of the string
def multilineString1 = """This is a really long multiline String.
In Java we would have to break up such
String into multiple Strings"""

def multilineString2 = '''This is a really long multiline String.
In Java we would have to break up such
String into multiple Strings'''

println multilineString1
println multilineString2

//In Groovy Strings can also be enclosed within / /, These are used in regular
//expressions because the backslash character does not need to be escaped in
//such Strings
def slashyString1 = / This String does not need to escape the \ character. /
def slashyString2 = / Even \n does not represent a newline /
println slashyString1 + ' ' + slashyString2

//Use == for String comparisons. Also note that double quoted Strings can
//contain single quotes
println "Is '${string1}' == '${string2}' : " + (string1 == string2)

//Groovy supports operator overloading
println 'Hello ' + "World"

//* repeats the String n times
println 'Hello ' * 3 + 'World'

//- removes the specifies substring starting from the left
println string1 - 'world'
println string1 - 'hello'
def stringOps = 'hello ' * 3 + ' world'
println stringOps - 'hello'

//Thankfully the divide operator is not supported with Strings
//println stringOps / 'hello'

//String can be directlt tokenized. We get a List type as the return
def list = multilineString1.tokenize("\n")

//Even though we will learn about ranges and lists later, here is a small
//example which shows how we can treat Strings like ranges and lists

//A String can also be accessed like a list with the [] operator
println string1[0]

//Strings can also be treated as ranges
println string1[1..5]

//ranges can also accept negative values
println string1[-5..-1]

//Strings can be centered for printing
println "'" + + "'"

//The String class overrides the << string3 =" string1">


Popular posts from this blog

My HSQLDB schema inspection story

This is a simple story of my need to inspect the schema of an HSQLDB database for a participar FOREIGN KEY, and the interesting things I had to do to actually inspect it. I am using an HSQLDB 1.8 database in one of my web applications. The application has been developed using the Play framework , which by default uses JPA and Hibernate . A few days back, I wanted to inspect the schema which Hibernate had created for one of my model objects. I started the HSQLDB database on my local machine, and then started the database manager with the following command java -cp ./hsqldb- org.hsqldb.util.DatabaseManagerSwing When I tried the view the schema of my table, it showed me the columns and column types on that table, but it did not show me columns were FOREIGN KEYs. Image 1: Table schema as shown by HSQLDB's database manager I decided to search on StackOverflow and find out how I could view the full schema of the table in question. I got a few hints, and they all pointed to

Fuctional Programming Principles in Scala - Getting Started

Sometime back I registered for the Functional Programming Principles in Scala , on Coursera. I have been meaning to learn Scala from a while, but have been putting it on the back burner because of other commitments. But  when I saw this course being offered by Martin Odersky, on Coursera , I just had to enroll in it. This course is a 7 week course. I will blog my learning experience and notes here for the next seven weeks (well actually six, since the course started on Sept 18th). The first step was to install the required tools: JDK - Since this is my work machine, I already have a couple of JDK's installed SBT - SBT is the Scala Build Tool. Even though I have not looked into it in detail, it seems like a replacement for Maven. I am sure we will use it for several things, however upto now I only know about two uses for it - to submit assignments (which must be a feature added by the course team), and to start the Scala console. Installed sbt from here , and added the path

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. -- 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