Java using groovy class

Differences with Java

Groovy tries to be as natural as possible for Java developers. We’ve tried to follow the principle of least surprise when designing Groovy, particularly for developers learning Groovy who’ve come from a Java background.

Here we list all the major differences between Java and Groovy.

1. Default imports

All these packages and classes are imported by default, i.e. you do not have to use an explicit import statement to use them:

• java.io.*
• java.lang.*
• java.math.BigDecimal
• java.math.BigInteger
• java.net.*
• java.util.*
• groovy.lang.*
• groovy.util.*

2. Multi-methods

In Groovy, the methods which will be invoked are chosen at runtime. This is called runtime dispatch or multi-methods. It means that the method will be chosen based on the types of the arguments at runtime. In Java, this is the opposite: methods are chosen at compile time, based on the declared types.

The following code, written as Java code, can be compiled in both Java and Groovy, but it will behave differently:

int method(String arg) < return 1; >int method(Object arg) < return 2; >Object o = "Object"; int result = method(o);

That is because Java will use the static information type, which is that o is declared as an Object , whereas Groovy will choose at runtime, when the method is actually called. Since it is called with a String , then the String version is called.

3. Array initializers

In Java, array initializers take either of these two forms:

int[] array = ; // Java array initializer shorthand syntax int[] array2 = new int[] ; // Java array initializer long syntax

In Groovy, the < …​ >block is reserved for closures. That means that you cannot create array literals using Java’s array initializer shorthand syntax. You instead borrow Groovy’s literal list notation like this:

For Groovy 3+, you can optionally use the Java’s array initializer long syntax:

def array2 = new int[] // Groovy 3.0+ supports the Java-style array initialization long syntax

4. Package scope visibility

In Groovy, omitting a modifier on a field doesn’t result in a package-private field like in Java:

Instead, it is used to create a property, that is to say a private field, an associated getter and an associated setter.

It is possible to create a package-private field by annotating it with @PackageScope :

5. ARM blocks

Java 7 introduced ARM (Automatic Resource Management) blocks (also know as try-with-resources) blocks like this:

Path file = Paths.get("/path/to/file"); Charset charset = Charset.forName("UTF-8"); try (BufferedReader reader = Files.newBufferedReader(file, charset)) < String line; while ((line = reader.readLine()) != null) < System.out.println(line); >> catch (IOException e)

Such blocks are supported from Groovy 3+. However, Groovy provides various methods relying on closures, which have the same effect while being more idiomatic. For example:

new File('/path/to/file').eachLine('UTF-8')

or, if you want a version closer to Java:

new File('/path/to/file').withReader('UTF-8') < reader ->reader.eachLine < println it >>

6. Inner classes

The implementation of anonymous inner classes and nested classes follow Java closely, but there are some differences, e.g. local variables accessed from within such classes don’t have to be final. We piggyback on some implementation details we use for groovy.lang.Closure when generating inner class bytecode.

6.1. Static inner classes

Here’s an example of static inner class:

The usage of static inner classes is the best supported one. If you absolutely need an inner class, you should make it a static one.

6.2. Anonymous Inner Classes

import java.util.concurrent.CountDownLatch import java.util.concurrent.TimeUnit CountDownLatch called = new CountDownLatch(1) Timer timer = new Timer() timer.schedule(new TimerTask() < void run() < called.countDown() >>, 0) assert called.await(10, TimeUnit.SECONDS)

6.3. Creating Instances of Non-Static Inner Classes

public class Y < public class X <>public X foo() < return new X(); >public static X createX(Y y) < return y.new X(); >>

Before 3.0.0, Groovy doesn’t support the y.new X() syntax. Instead, you have to write new X(y) , like in the code below:

public class Y < public class X <>public X foo() < return new X() >public static X createX(Y y) < return new X(y) >>

Caution though, Groovy supports calling methods with one parameter without giving an argument. The parameter will then have the value null. Basically the same rules apply to calling a constructor. There is a danger that you will write new X() instead of new X(this) for example. Since this might also be the regular way we have not yet found a good way to prevent this problem.

7. Lambda expressions and the method reference operator

Java 8+ supports lambda expressions and the method reference operator ( :: ):

Runnable run = () -> System.out.println("Run"); // Java list.forEach(System.out::println);

Groovy 3 and above also support these within the Parrot parser. In earlier versions of Groovy you should use closures instead:

Runnable run = < println 'run' >list.each < println it >// or list.each(this.&println)

8. GStrings

As double-quoted string literals are interpreted as GString values, Groovy may fail with compile error or produce subtly different code if a class with String literal containing a dollar character is compiled with Groovy and Java compiler.

While typically, Groovy will auto-cast between GString and String if an API declares the type of a parameter, beware of Java APIs that accept an Object parameter and then check the actual type.

9. String and Character literals

Singly-quoted literals in Groovy are used for String , and double-quoted result in String or GString , depending whether there is interpolation in the literal.

assert 'c'.class == String assert "c".class == String assert "c$".class in GString

Groovy will automatically cast a single-character String to char only when assigning to a variable of type char . When calling methods with arguments of type char we need to either cast explicitly or make sure the value has been cast in advance.

char a = 'a' assert Character.digit(a, 16) == 10: 'But Groovy does boxing' assert Character.digit((char) 'a', 16) == 10 try < assert Character.digit('a', 16) == 10 assert false: 'Need explicit cast' >catch(MissingMethodException e)

Groovy supports two styles of casting and in the case of casting to char there are subtle differences when casting a multi-char strings. The Groovy style cast is more lenient and will take the first character, while the C-style cast will fail with exception.

// for single char strings, both are the same assert ((char) "c").class == Character assert ("c" as char).class == Character // for multi char strings they are not try < ((char) 'cx') == 'c' assert false: 'will fail - not castable' >catch(GroovyCastException e) < >assert ('cx' as char) == 'c' assert 'cx'.asType(char) == 'c'

10. Behaviour of ==

In Java, == means equality of primitive types or identity for objects. In Groovy, == means equality in all places. For non-primitives, it translates to a.compareTo(b) == 0 , when evaluating equality for Comparable objects, and a.equals(b) otherwise.

To check for identity (reference equality), use the is method: a.is(b) . From Groovy 3, you can also use the === operator (or negated version): a === b (or c !== d ).

11. Primitives and wrappers

In a pure object-oriented language, everything would be an object. Java takes the stance that primitive types, such as int, boolean and double, are used very frequently and worthy of special treatment. Primitives can be efficiently stored and manipulated but can’t be used in all contexts where an object could be used. Luckily, Java auto boxes and unboxes primitives when they are passed as parameters or used as return types:

public class Main < // Java float f1 = 1.0f; Float f2 = 2.0f; float add(Float a1, float a2) < return a1 + a2; >Float calc() < return add(f1, f2); >(1) public static void main(String[] args) < Float calcResult = new Main().calc(); System.out.println(calcResult); // =>3.0 > >

1	The add method expects wrapper then primitive type arguments, but we are supplying parameters with a primitive then wrapper type. Similarly, the return type from add is primitive, but we need the wrapper type.

class Main < float f1 = 1.0f Float f2 = 2.0f float add(Float a1, float a2) < a1 + a2 >Float calc() < add(f1, f2) >> assert new Main().calc() == 3.0

Groovy, also supports primitives and object types, however, it goes a little further in pushing OO purity; it tries hard to treat everything as an object. Any primitive typed variable or field can be treated like an object, and it will be auto-wrapped as needed. While primitive types might be used under the covers, their use should be indistinguishable from normal object use whenever possible, and they will be boxed/unboxed as needed.

Here is a little example using Java trying to (incorrectly for Java) dereference a primitive float :

The same example using Groovy compiles and runs successfully:

class Main < float z1 = 0.0f >assert !(new Main().z1.equals(1.0f))

Because of Groovy’s additional use of un/boxing, it does not follow Java’s behavior of widening taking priority over boxing. Here’s an example using int

int i m(i) void m(long l) (1) println "in m(long)" > void m(Integer i) (2) println "in m(Integer)" >

1	This is the method that Java would call, since widening has precedence over unboxing.
2	This is the method Groovy actually calls, since all primitive references use their wrapper class.

11.1. Numeric Primitive Optimisation with @CompileStatic

Since Groovy converts to wrapper classes in more places, you might wonder whether it produces less efficient bytecode for numeric expressions. Groovy has a highly optimised set of classes for doing math computations. When using @CompileStatic , expressions involving only primitives uses the same bytecode that Java would use.

11.2. Positive/Negative zero edge case

Java float/double operations for both primitives and wrapper classes follow the IEEE 754 standard but there is an interesting edge case involving positive and negative zero. The standard supports distinguishing between these two cases and while in many scenarios programmers may not care about the difference, in some mathematical or data science scenarios it is important to cater for the distinction.

For primitives, Java maps down onto a special bytecode instruction when comparing such values which has the property that «Positive zero and negative zero are considered equal».

jshell> float f1 = 0.0f f1 ==> 0.0 jshell> float f2 = -0.0f f2 ==> -0.0 jshell> f1 == f2 $3 ==> true

For the wrapper classes, e.g. java.base/java.lang.Float#equals(java.lang.Object), the result is false for this same case.

jshell> Float f1 = 0.0f f1 ==> 0.0 jshell> Float f2 = -0.0f f2 ==> -0.0 jshell> f1.equals(f2) $3 ==> false

Groovy on the one hand tries to follow Java behavior closely, but on the other switches automatically between primitives and wrapped equivalents in more places. To avoid confusion we recommend the following guidelines:

• If you wish to distinguish between positive and negative zero, use the equals method directly or cast any primitives to their wrapper equivalent before using == .
• If you wish to ignore the difference between positive and negative zero, use the equalsIgnoreZeroSign method directly or cast any non-primitives to their primitive equivalent before using == .

These guidelines are illustrated in the following example:

float f1 = 0.0f float f2 = -0.0f Float f3 = 0.0f Float f4 = -0.0f assert f1 == f2 assert (Float) f1 != (Float) f2 assert f3 != f4 (1) assert (float) f3 == (float) f4 assert !f1.equals(f2) assert !f3.equals(f4) assert f1.equalsIgnoreZeroSign(f2) assert f3.equalsIgnoreZeroSign(f4)

Источник