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 "'" + string1.center(25) + "'"

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

Comments

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

Commenting your code

Comments are an integral part of any program, even though they do not contribute to the logic. Appropriate comments add to the maintainability of a software. I have heard developers complain about not remembering the logic of some code they wrote a few months back. Can you imagine how difficult it can be to understand programs written by others, when we sometimes find it hard to understand our own code. It is a nightmare to maintain programs that are not appropriately commented. Java classes should contain comments at various levels. There are two types of comments; implementation comments and documentation comments. Implementation comments usually explain design desicisions, or a particularly intricate peice of code. If you find the need to make a lot of implementation comments, then it may signal overly complex code. Documentation comments usually describe the API of a program, they are meant for developers who are going to use your classes. All classes, methods and variables ...

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