Re: class gc

Date view Thread view Subject view Author view

From: Godmar Back (gback@cs.utah.edu)
Date: Thu Dec 17 1998 - 15:44:46 EST


>
> On Dec 17, 1998, Godmar Back <gback@cs.utah.edu> wrote:
>
> > Do you mean the static classFinalize method that early versions of the
> > JLS wanted you to invoke? This thing's gone.
>
> Yep. How about
> http://java.sun.com/docs/books/jls/html/12.doc.html#48744
>
> It's still listed in the documentation of JDK 1.2.

 Where?

My info is from here:
http://java.sun.com/docs/books/jls/class-finalization-rationale.html

>
> > As for threads, all functions can actually deal with destroyed threads
> > because that's exactly the state that they're in before they're started.
>
> Good. But how about File*Streams?

Same there, actually --- fd is set to -1.
But I will read your mail again and see if I understand your proposal
because in principle, we do want to deal with the problem.

>
> >> > Note that classes keep their loader alive, while the loader does
> >> > not (per se) keep the classes alive.
>
> >> Shouldn't it maintain a hashtable pointing to all classes, so as to
> >> (as a side effect) keep them all alive?
>
> > This is what the class entry pool does.
>
> So the ClassLoader actually keeps its Classes alive, via the class
> entry pool? If it does not, I think it should.
>

 So it does keep them alive since the class entry pool is not walked.

Tell me why it should.

        - Godmar


Date view Thread view Subject view Author view

This archive was generated by hypermail 2b29 : Sat Sep 23 2000 - 19:57:20 EDT