Skip to main content

Groovy numbers

I was very pleasantly surprised when I learned how to work with numbers in Groovy. The first difference between Groovy and Java (while dealing with numbers) is that in Groovy numbers are always objects. There are no primitive numbers like in Java. This may have the disadvantage of increased memory usage, but it also has the advantage that working with large numbers is much easier.

If you have tried doing high precision calculations or working with really large numbers in Java, then you know how difficult it is to work with BigDecimal and BigInteger to perform calculations. We have to call methods instead of using operators. Let's see this with a small example. If I want to print the value of Long.MAX_VALUE * 2, I have to use BigInteger and then invoke it's multiply method as shown in the example below:

System.out.println(Long.MAX_VALUE * 2); //Incorrect: prints -2
//The right way to work with large numbers in Java
BigInteger bi1 = new BigInteger("9223372036854775807");
BigInteger bi2 = new BigInteger("2");
BigInteger bi3 = bi1.multiply(bi2);
System.out.println(bi3);

Output of this program is:

-2
18446744073709551614


See how cumbersome it is to do even simple operations with integers larger than 263-1. However in Groovy, multiplying Long.MAX_VALUE with 2 would have automatically resulted in a BigInteger. Floating point numbers in Groovy are always BigDecimals, and as a rule, when we do arithmetic operations in Groovy, the result is always what we expect it to be.

This small snippet of Groovy code is self explanatory.


//It is very natural to do high precision calculations in Groovy because
//in Groovy numbers can be directly represented with BigDecimal and BigInteger
//and we can use regular arithmatic operators with them

//Numbers in Groovy are first class objects
def i = 5
println '5 is of type ' + i.getClass().getName()

def d = 5.4
println '5.4 is of type ' + d.getClass().getName()

//It is possible to explicitly create Long, Float, Double, and G???
def l = 8999000000000L
println '8999000000000L is of type ' + l.getClass().getName()

def f = 1.2F
println '1.2F is of type ' + f.getClass().getName()

def doubleObj = 1.2D
println '1.2D is of type ' + doubleObj.class.getName()

def g = 3G
def g1 = 3.5G
println '3G is of type ' + g.getClass().getName()
println '3.5G is of type ' + g1.getClass().getName()

//type conversions in arithmatic operations
//Mostly the result is what you would expect
println 'Adding Integers results in a : ' + (3 + 3).class.getName()
println 'Multiplying Integers results in a : ' + (3*3).class.getName()
println 'subtraction between Integers results in a : ' + (3-8).class.getName()
println 'Division of an Integer with an Integer results in a : ' + (3/3).class.getName()

//Integer division can be forced with the intdiv() method
def fi = 1.intdiv(2)
println 'fi is of type: ' + fi.class.getName() + ' and it\'s value is ' + fi

//Some numbers also have methods which can be used instead of for loops
//by accepting a closure
def n = 5
n.times { print """${it} """} //notice the use of GStrings

//other methods on numbers include upto, downto, and step
//we also need a more advanced example on numbers to explore all the other
//methods present in various number classes


Output of this program is:

5 is of type java.lang.Integer
5.4 is of type java.math.BigDecimal
8999000000000L is of type java.lang.Long
1.2F is of type java.lang.Float
1.2D is of type java.lang.Double
3G is of type java.math.BigInteger
3.5G is of type java.math.BigDecimal
Adding Integers results in a : java.lang.Integer
Multiplying Integers results in a : java.lang.Integer
subtraction between Integers results in a : java.lang.Integer
Division of an Integer with an Integer results in a : java.math.BigDecimal
fi is of type: java.lang.Integer and it's value is 0
0 1 2 3 4

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

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