Java Code Static Final variable usage

Question

I've got two classes below. Both have one variable 'reply' with a getter. There is no setter method for this variable. Only difference is in ClassOne, the variable is static final.

So whats the difference and which one is preferred?

public class ClassOne {

    private static final String reply = "Success";
    ..

    public String getReply() {
        return reply;
    }

    // no setter

}

and Class 2

public class ClassTwo {

    private String reply = "Success";
    ..

    public String getReply() {
        return reply;
    }

    // no setter
}

UPDATE 1:

What I want to know is that when there is no setter for a variable, should the variable be declared as static final for optimization? or does it not matter?

You could start by reading a good tutorial.

assylias
– assylias

2012-09-13 09:09:06 +00:00
Commented Sep 13, 2012 at 9:09 — assylias
– assylias, Commented Sep 13, 2012 at 9:09

assylias · Accepted Answer · 2012-09-13 09:29:06Z

5

should the variable be declared as static final for optimization?

final certainly, not only for optimization but for clarity and because it can make your object immutable, which is always a good thing to have.
static completely changes the nature of the field and has nothing to do with the existence of setters: do you want only one instance of that field, or do you need one per instance of your class?
Non static example: a Person has a name, which is a constant (for a given person = per instance), so you can use a non static final field, which you only set once when creating a new Person:

        private final String name;

Static example: Whenever you don't have a name for a Person, you want to use a default value - that is a global constant which is shared among all persons that don't have a name and you can use a static final field:

        private static final String NO_NAME = "John Doe";

edited Sep 13, 2012 at 9:29

answered Sep 13, 2012 at 9:17

assylias

330k84 gold badges680 silver badges806 bronze badges

Sign up to request clarification or add additional context in comments.

1 Comment

adi Over a year ago

Static: If there is no setter and I do not intend to change it value once set, should it be static then? If the value is not changing, why would I want it one per instance?

vainolo · Accepted Answer · 2012-09-13 09:04:36Z

3

When you set the variable as final, you are telling everybody (the compiler, the runtime) that it cannot be changed. This can help a lot with optimizations like inlining all of the occurrences of the variable with its value.

answered Sep 13, 2012 at 9:04

vainolo

7,0074 gold badges26 silver badges48 bronze badges

Comments

Philipp · Accepted Answer · 2012-09-13 09:06:45Z

2

When you have a constant string which can not be changed, you should make it a static final string.

Static means that less memory is needed for instance of the class, because the instances don't need individual copies.

Final allows some optimizations and thus makes your program faster.

answered Sep 13, 2012 at 9:06

Philipp

70.1k10 gold badges121 silver badges159 bronze badges

Comments

Gaim · Accepted Answer · 2012-09-13 09:07:31Z

2

There are few things good to know:

final variables can be checked by compiler that they are not accidentally changed.
references to non-static variables are contained in instance so there is small needless memory consumption in addition
static variables are shared across all instances of the same class, so you can be sure that all instances work with the same value
final static variables, especially the Strings are linked in compilation time so they need not to be dereferenced at runtime from the field. Due to that it cannot be changed even by the reflection, because such field is not used at runtime.

answered Sep 13, 2012 at 9:07

Gaim

6,8545 gold badges40 silver badges59 bronze badges

Comments

Brian Agnew · Accepted Answer · 2012-09-13 09:29:36Z

Setting the reference to final ensures you can't change the reference. Note however that if the object referred to is mutable then you could still change that (not in this instance, since Strings are immutable).

I normally make fields final and initialise them in the constructor. By favouring immutability my classes are easier to debug and are more likely to be safe in threaded environments. It's easier to remove the immutability constraint than add it.

I also do this for method arguments. Rarely (ever) do I want to change a method argument, and making them final will catch inadvertent assignments.

I try not to use static except for final constants. Unless it's something like a logger, I don't really want one instance per class, and (of course) this doesn't work in the case of multiple classloaders. It's also getting close to the singleton anti-pattern, and this impacts on easy testing and (potentially) threading.

manub · Accepted Answer · 2012-09-13 09:07:01Z

1

The fact that you make the variable static means that a single instance of that variable will be shared among all the instances of ClassOne, as the variable is bound to the class itself, not to its instances. Apart from any JVM optimisations, you'll have a single instance of reply for every instance of ClassTwo.

answered Sep 13, 2012 at 9:07

manub

4,1102 gold badges27 silver badges35 bronze badges

Comments

Amit Deshpande · Accepted Answer · 2012-09-13 09:13:19Z

1

First one is Constant you need to know value of it at compile time.

private static final String reply = "Success";

second is just simple member variable. So any case first one is preferred since second one will create value for each object.

Assuming that you intended **private final String reply** in second case

A final variable can only be initialized once, either via an initializer or an assignment statement. It does not need to be initialized at the point of declaration: this is called a "blank final" variable.

In second case you can also declare and initialize it in constructor

 private final String reply;

You can read more about it here

answered Sep 13, 2012 at 9:13

Amit Deshpande

19.2k4 gold badges48 silver badges72 bronze badges

Collectives™ on Stack Overflow

Java Code Static Final variable usage

7 Answers 7

1 Comment

Comments

Comments

Comments

Comments

Comments

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

7 Answers 7

1 Comment

Comments

Comments

Comments

Comments

Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Related