creating a new instance

[Tony Johansson]

Hello!!

Here I create a new instance t of class Test and pass the referenc to method
goo.
When this method foo eventually finish will this instace t go out of scope
and be garbage collected.?
If not exactly what must occur so that the instance t be garbage collected.

void foo()
{
Test t = new Test;
goo(t);
}

//Tony

[Claus Petersen]

"Tony Johansson" <jo*****************@telia.com> skrev i en meddelelse
news:QC*********************@newsc.telia.net...

Hello!!

Here I create a new instance t of class Test and pass the referenc to
method goo.
When this method foo eventually finish will this instace t go out of scope
and be garbage collected.?
If not exactly what must occur so that the instance t be garbage
collected.

void foo()
{
Test t = new Test;
goo(t);
}

//Tony

Short anwer: YES.......

But if you want to be sure, then set t = null; after the call to goo
Claus

[Casper B]

> But if you want to be sure, then set t = null; after the call to goo

And (assuming everything is syncronous) if you REALLY want to be in
control, call the garbage collector explicitly:

System.gc();

/Casper

[Raymond DeCampo]

Claus Petersen wrote:

"Tony Johansson" <jo*****************@telia.com> skrev i en meddelelse
news:QC*********************@newsc.telia.net...

Hello!!

Here I create a new instance t of class Test and pass the referenc to
method goo.
When this method foo eventually finish will this instace t go out of scope
and be garbage collected.?
If not exactly what must occur so that the instance t be garbage
collected.

void foo()
{
Test t = new Test;
goo(t);
}

//Tony

Short anwer: YES.......

But if you want to be sure, then set t = null; after the call to goo
Claus

It depends also on what goo() does. If goo() stores a reference
somewhere t may not be eligible for GC.

Ray

--
XML is the programmer's duct tape.

[Alex Molochnikov]

"Casper B" <ca****@jbr.dk> wrote in message
news:42*********************@dread12.news.tele.dk. ..

But if you want to be sure, then set t = null; after the call to goo

And (assuming everything is syncronous) if you REALLY want to be in
control, call the garbage collector explicitly:

System.gc();

/Casper

.... Except that the GC will never let you be in control. The call to
System.gc() is only a _suggestion_ to JVM to run the garbage collector. The
JVM may or may not do it on your request. Also, setting t to null is
superfluous. Once t goes out of scope in the given example, all references
to it are gone, and it becomes eligible for the collection - whether it was
nulled out or not.