garbage collection *resolved*

[mbonfyre]

could somebody explain how java uses garbage collection to reclaim unused memory space?

From reading that I have done, I am not sure which way it goes about it:

my example:

TownBuilding = new Building("Town Hall"); //(a)
TownBuilding = new Building("Public Library"); //(b)

When b is coded, does java simply overwrite the contents or does it create a new Variable (b) and leave (a) for garbage collection?

Very confused...

[CornedBee]

Not sure what you mean with your question, so here are two answers.

1 (simple)
Non-primitive variables in Java aren't the objects, they are only references. When you do a new, the VM creates an actual object on the heap and returns a reference to it, which you can then assign to a reference you declared and use the object through it.
When you assign a new value to the reference, the old object lies on the heap waiting for GC.

2 (advanced)
There is no object reuse unless you explicitly implement it for a class (via a static factory method). An exception might be java.lang.String, depending on the JVM implementation.

[Dillinger4]

Yes CornedBee is right. Also, scope dictates when an object or objects are eligible for garbage collection. For the two objects you have created there would be no overwriting of data. Both objects would reside in memory as two seperate objects with any static member variables being shared by both.

TownBuilding t1 = new Building("Town Hall"); //(a)
TownBuilding t2 = new Building("Public Library"); //(b)