This week's book giveaway is in the Design forum.
We're giving away four copies of Building Microservices and have Sam Newman on-line!
See this thread for details.
The moose likes Java in General and the fly likes why I must use final modifier Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login

Win a copy of Building Microservices this week in the Design forum!
JavaRanch » Java Forums » Java » Java in General
Bookmark "why I must use final modifier" Watch "why I must use final modifier" New topic

why I must use final modifier

Jimsecond Huang

Joined: Dec 03, 2004
Posts: 8

Just test some code below,

public static void main(String[] args){
final HelloWorldSwing hws = new HelloWorldSwing();
javax.swing.SwingUtilities.invokeLater(new Runnable() {
public void run() {
The ide ask me to add final modifier for variable hws. I don't know why this is mandatory.

anyone knows

Ernest Friedman-Hill
author and iconoclast

Joined: Jul 08, 2003
Posts: 24190

Because hwe is a local variable, the stack frame it's defined in may not even exist by the time the run() method is actually invoked. My making the variable final, you're actually giving Java permission to take a copy of the variable's value at the time the inner class object is created, and use that copy, rather than having to go find a (possibly non-existent) value when the run() method runs.

[Jess in Action][AskingGoodQuestions]
Jimsecond Huang

Joined: Dec 03, 2004
Posts: 8

Thanks so much. I just think I got it but your answer is so perfect.

I agree. Here's the link:
subject: why I must use final modifier
It's not a secret anymore!