Re: class finalizer?

1999-01-15 Thread Jason Dillon
hrm... that is very annoying... thanks. --jason On 15-Jan-99 Chris Abbey wrote: > DOH! The signature was supposed to be: > static void classFinalize() throws Throwable > the one I gave was (obviously) instance finalization... see JLS §12.7. > > But it's a academic now, Javasoft has removed it f

Re: class finalizer?

1999-01-14 Thread Chris Abbey
DOH! The signature was supposed to be: static void classFinalize() throws Throwable the one I gave was (obviously) instance finalization... see JLS §12.7. But it's a academic now, Javasoft has removed it from the JLS -- see http://java.sun.com/docs/books/jls/class-finalization-rationale.html for

Re: class finalizer?

1999-01-14 Thread Jason Dillon
a static finalize method causes the compiler (jikes in this case) to return: 93. public static void finalize () <-> *** Error: The static method "void finalize();" cannot hide the instance method --jason On 14-Jan-99 Chris Abbey wrote: >>Is there

Re: class finalizer?

1999-01-13 Thread Chris Abbey
>Is there any way to detect when a class is going to be unloaded from the vm >sort of the opposite of static { ... }? > >--jason In theory or in practice? In theory the JLS says so, put a static method finalize() in the class (sorry, don't remember the protection, maybe public??) and the VM

class finalizer?

1999-01-13 Thread Jason Dillon
Is there any way to detect when a class is going to be unloaded from the vm sort of the opposite of static { ... }? --jason

Re: (long) finalizer() - potential bug

1999-01-07 Thread Chris Abbey
At 12:32 PM 1/7/99 +0100, Chr. Clemens Lahme wrote: >when I added a System.exit( 0 ) call to main, jre does work for me. Oi. I got the same results. So now there is DIFFERENT behaviour on between the java and jre runners . . . just peachy. I'm going to have a look into that might be a bug to

finalizer() - BUG!

1999-01-07 Thread Chris Abbey
John, At this point I'd say they've got a bug in the version you have installed on possum, "Linux_JDK_1.1.7_v1a_green_threads", but not on the one on emu, "stevemw:08/29/98-05:16". I hate to add a variable at this point... but what about native threaded?? -=Chris At 07:04 AM 1/8/99 +0800, John S

Re: (long) finalizer() - potential bug

1999-01-07 Thread John Summerfield
ne 9 to this: System.out.print("\nfinalize\n"); as I got some output (on emu) and "finalize" was separated from its followong newline. Since it works on emu running with java_g, I'm not posting its trace. > John's understanding of finalizer and runFinalizersOn

Re: (long) finalizer() - potential bug

1999-01-07 Thread Chr. Clemens Lahme
As someone else mentioned the test code did work for me with jdk1.1.7 v1a with java, but not with jre. Just wanted to add, that, when I added a System.exit( 0 ) call to main, jre does work for me. Bye, Clemes Changed test example: public class F { protected void finalize() throws T

(long) finalizer() - potential bug

1999-01-06 Thread Chris Abbey
John (& all), Sorry I didn't jump into this thread earlier, but the s:n on this list has pushed it down my reading priority list ... way down. John's understanding of finalizer and runFinalizersOnExit as I've understood him to state it in this thread matches my

Re: finalizer()

1999-01-06 Thread John Summerfield
the > objects that must be finalized: in the constructor, add the new object > to a Vector; when you're done with one run the finalizer yourself. I CAN call the finalizer() mtself. However, I'm trying to write a class that will clean itself up without the programmer having to remem

Re: finalizer()

1999-01-06 Thread SHUDO Kazuyuki
daniel dulitz wrote: > If (as someone else indicated) Sun's JVM uses a conservative garbage > collector, then even though one may force garbage collection, there's > no way to force the garbage collector to recognize that a particular > object is in fact garbage. Sun's JVM, at least JDK 1.0.X an

Re: finalizer()

1999-01-05 Thread Daniel W. Dulitz x108
ld be very difficult (or impossible) to achieve with a conservative garbage collector. There is a workaround, if you don't need to garbage collect the objects that must be finalized: in the constructor, add the new object to a Vector; when you're done with one run the finalizer yo

Re: finalizer()

1999-01-05 Thread John Summerfield
On Tue, 5 Jan 1999, Catalin CLIMOV wrote: > Very strange. > I tried to run your code and it worked fine with java (it displayed 'finelize'), > but it didn't work with jre (it finished without displaying anything). > I use the same jdk on Linux 5.1, kernel 2.0.34. I thought this was it as I use j

Re: finalizer()

1999-01-05 Thread Eduard Boukhman
On Jan 5, 1:30pm, Eduard Boukhman wrote: > Subject: Re: finalizer() > On Jan 5, 1:22pm, Catalin CLIMOV wrote: > > Subject: Re: finalizer() > > Very strange. > > I tried to run your code and it worked fine with java (it displayed > 'finelize'), > &g

Re: finalizer()

1999-01-05 Thread Eduard Boukhman
On Jan 5, 1:22pm, Catalin CLIMOV wrote: > Subject: Re: finalizer() > Very strange. > I tried to run your code and it worked fine with java (it displayed 'finelize'), > but it didn't work with jre (it finished without displaying anything). > I use the same j

Re: finalizer()

1999-01-05 Thread Catalin CLIMOV
Very strange. I tried to run your code and it worked fine with java (it displayed 'finelize'), but it didn't work with jre (it finished without displaying anything). I use the same jdk on Linux 5.1, kernel 2.0.34. Catalin CLIMOV. John Summerfield wrote: > I have this code: > public class F >

finalizer()

1999-01-05 Thread John Summerfield
I have this code: public class F { protected void finalize() throws Throwable { System.out.println("finalize"); super.finalize(); } public static void main(String[] args) throws Throwable { F f = new F(); Sy