• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

Method-Local Inner Class and Local Variable

 
Greenhorn
Posts: 18
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

The local variables of the method live on the stack, and exist only for
the lifetime of the method. You already know that the scope of a local variable is
limited to the method the variable is declared in. When the method ends, the stack
frame is blown away and the variable is history. But even after the method
completes, the inner class object created within it might still be alive on the heap if,
for example, a reference to it was passed into some other code and then stored in an
instance variable. Because the local variables aren't guaranteed to be alive as long
as the method-local inner class object, the inner class object can't use them. Unless
the local variables are marked final!



Why M-LIC can access a final marked variable and not a simple variable?
If the problem is the life cycle of the local variable - the variable die with the stack of method -, why a final don�t die ?
 
author
Posts: 23949
142
jQuery Eclipse IDE Firefox Browser VI Editor C++ Chrome Java Linux Windows
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

Originally posted by Mateus Brum:

Why M-LIC can access a final marked variable and not a simple variable?
If the problem is the life cycle of the local variable - the variable die with the stack of method -, why a final don�t die ?



M-LIC? Please don't make up acronyms. It makes your question harder to understand. And I am assuming that you want people to actually understand your question, right?


As for your question, it is just how it is specified. Java will make a copy of the local variable for the inner class, but the inner class doesn't know that it is a copy. This way, it is no longer tied to the scope of the method.

But, for it to work, the spec requires that the original value doesn't change -- meaning that it is final.

Henry
 
Sheriff
Posts: 11343
Mac Safari Java
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

Originally posted by Henry Wong:
... M-LIC? ...


This is clearly meant to indicate a class M (Motorcycle) driver's license.

But seriously, I would like to see a source cited for this quote.
reply
    Bookmark Topic Watch Topic
  • New Topic