Collectives™ on Stack Overflow

Find centralized, trusted content and collaborate around the technologies you use most.

Learn more about Collectives

Teams

Q&A for work

Connect and share knowledge within a single location that is structured and easy to search.

Learn more about Teams

Cannot reference "X" before supertype constructor has been called, where x is a final variable

Ask Question public Test() { this(defaultValue); // <-- Compiler error: cannot reference defaultValue before supertype constructor has been called. public Test(int i) { var = i;

The code will not compile, with the compiler complaining about the line I've highlighted above. Why is this error happening and what's the best workaround?

The reason why the code would not initially compile is because defaultValue is an instance variable of the class Test , meaning that when an object of type Test is created, a unique instance of defaultValue is also created and attached to that particular object. Because of this, it is not possible to reference defaultValue in the constructor, as neither it, nor the object have been created yet.

The solution is to make the final variable static :

public class Test {
    private static final int defaultValue = 10;
    private int var;
    public Test() {
        this(defaultValue);
    public Test(int i) {
        var = i;

By making the variable static, it becomes associated with the class itself, rather than instances of that class and is shared amongst all instances of Test. Static variables are created when the JVM first loads the class. Since the class is already loaded when you use it to create an instance, the static variable is ready to use and so can be used in the class, including the constructor.

References:

  • Forum post asking the same question
  • Understanding Instance and Class Members
  • Explanation of how classloader loads static variables
  • No, an object is created when the root constructor in the constructor chain (that is the Object class constructor) executes. It it were created only after (ordinary) constructor having finished, then its fields were unavailable during the constructor execution. In this example, the intermediate constructor Test(int i) references the field var, which already exists. – John McClane Jul 28, 2018 at 7:30

    It is because the defaultValue is an member of Test 's instance which is under construction (not yet created)

    If you had it static it were loaded when your class loads by classloaders

    You are referencing to a variable that doesn't exist yet, if it was static it would exist even before the constructor itself.

    But you will face another problem, as defaultValue became static, so all other instances may share the same value which you may don't like it to be:

    public class Test {
        private final int defaultValue = 10; //this will exist only after calling the constructor
        private final static int value2= 10; //this exists before the constructor has been called
        private int var;
        public Test() {
           // this(defaultValue);    // this method will not work as defaultValue doesn't exist yet
        this(value2); //will work
        //this(10); will work
        public Test(int i) {
            var = i;
    

    Rule : Every constructor must execute super class's constructor before executing itself.

    So the first line of every constructor is super() or may be this() and you are send the defaultValue to the this class constructor which(defaultValue) is not existed yet hence there is compile time error.

    You can made defaultValue as static and since static variable is created as class is loaded to memory so defaultValue is available at the line this(defaultValue).

    Thanks for contributing an answer to Stack Overflow!

    • Please be sure to answer the question. Provide details and share your research!

    But avoid

    • Asking for help, clarification, or responding to other answers.
    • Making statements based on opinion; back them up with references or personal experience.

    To learn more, see our tips on writing great answers.