anon inner class

public class MyApp2{
public MyApp2(){

JFrame frame = new JFrame ("My App");
JTextField tf = new JTextField();
JButton button = new JButton("ok");
button.addActionListener(
new ActionListener(){
public void actionPerformed(ActionEvent event){
System.out.println(tf.getText());
}
}


);
}
}


Assume everything has been imported etc.

Can someone explain why the textfield tf has to be declared as final, I don't understand why.

Thanks for your time

This ensures the reference tf does not change, and so is not accidentally reflected in the inner class.
Something along the lines of:

Code:

---

JTextField tf = new JTextField();
myPanel.add(tf);
JButton button = new JButton("ok");
button.addActionListener(
    new ActionListener(){
        public void actionPerformed(ActionEvent event){
            System.out.println(tf.getText());
        }
    }
);
tf = new JTextField();
myPanel.add(tf);

---

It's possible that the action listener could be referring to the wrong text field.
So the desgners way back when in the 90s decided to avoid that whole question and simply insist that these references are final.

I wish I had the documentation on it that I read years ago, so I wouldn't have to rely on pure memory here...

Quote:

---

Originally Posted by Tolls

This ensures the reference tf does not change, and so is not accidentally reflected in the inner class.
Something along the lines of:

Code:

---

JTextField tf = new JTextField();
myPanel.add(tf);
JButton button = new JButton("ok");
button.addActionListener(
    new ActionListener(){
        public void actionPerformed(ActionEvent event){
            System.out.println(tf.getText());
        }
    }
);
tf = new JTextField();
myPanel.add(tf);

---

It's possible that the action listener could be referring to the wrong text field.
So the desgners way back when in the 90s decided to avoid that whole question and simply insist that these references are final.

I wish I had the documentation on it that I read years ago, so I wouldn't have to rely on pure memory here...

---

Thanks!!!

The reason could be because the variable is defined locally to method/constructor. The compiler wants a way to keep its value past the exiting of the method.

Quote:

---

Originally Posted by Norm

The compiler wants a way to keep its value past the exiting of the method.

---

What do you mean by this?

Local variables are gone when the enclosing method terminates but that class object survices and so everything that is used by that object still has to be there; marking local variables final ensures that they survice the termination of the method.

kind regards,

Jos

Quote:

---

Originally Posted by JosAH

Local variables are gone when the enclosing method terminates but that class object survices and so everything that is used by that object still has to be there; marking local variables final ensures that they survice the termination of the method.

kind regards,

Jos

---

Does this mean we always have to declare them as final???

No, you could make them member (aka instance) variables by simply changing where you declare them:

Code:

---

public class MyApp2{
  JFrame frame;
  JTextField tf;
  JButton button;

public MyApp2(){
  frame = new JFrame ("My App");
  tf = new JTextField();
  button = new JButton("ok");
  button.addActionListener(
      new ActionListener(){
        public void actionPerformed(ActionEvent event){
            System.out.println(tf.getText());
        }
      }
  );
}
}

---

But why did my intial one require the final declaration on it?

The variable's value would be gone when the method exited. Did you miss the explanations given earlier?

But if the new method cant see the variable tf, how does declaring as final make a difference?

See the previous posts.

So if we declare it as final it kind of becomes like an instance variable?

Sorry for being so slow but I'm just finding it confusing as there are so many different ways of doing things in java for the most simple cases.

Thanks for your patience

final makes its value available to the method in the anonymous class.

Variables (The Java™ Tutorials > Learning the Java Language > Language Basics)