Re: finalize() again

1999-01-06 Thread John Summerfield
to the finalize section for > Vector but that's up to SUN to do that. Neither of these is relevant to the code I posted. > > 3.Don't forget to do a super.finalize() in all subclasses at the last line in > void finalize() Again, not relevant to the code I posted (but

Re: finalize() again

1999-01-06 Thread mlorton
> I've put in checks in our code to check is things are getting finalized... It does > happen (eventually) > > To force cleanups, I rely on the following: > > 1.add a void kill() in all heavy classes. make it delete files, close > sockets... etc. I would use the word "dispose()" for thi

Re: finalize() again

1999-01-05 Thread nagendra mishr
I've put in checks in our code to check is things are getting finalized... It does happen (eventually) To force cleanups, I rely on the following: 1.add a void kill() in all heavy classes. make it delete files, close sockets... etc. 2.In void finalize() I make all references point

Re: finalize() again

1999-01-05 Thread Nigel Gamble
On Tue, 5 Jan 1999, Manfred Hauswirth wrote: > Even more confusing is the follwoing statement (Bug Id 4102959, State Closed, > will not be fixed) : > > "According to the bugs database, this is only the third time that anyone's > noticed that we've never implemented class finalization. -- >

finalize() again

1999-01-05 Thread Manfred Hauswirth
Though this is not directly Java-Linux related, I think it is important to mention this on this mailing list, since it is important to distinguish Java problems from Java-on-Linux problems (if there are problems with Java on Linux, people tend to blame it on Linux ...): The finalize() issue se