In java, finalization is not even guaranteed to occur.  If the GC never
removes the object the finalization never happens.  This makes finalization
rather useless in Java.

On the other hand, I programmed Java full-time for years and never once
thought "I wish I had a finalizer".

-----Original Message-----
From: Yukihiro Matsumoto [mailto:matz / ruby-lang.org]
Sent: Friday, November 23, 2001 4:52 PM
To: ruby-talk ML
Subject: [ruby-talk:26276] Re: [OT] Re: KDE or GNOME curiosity
question...


Hi,

In message "[ruby-talk:26236] Re: [OT] Re: KDE or GNOME curiosity
question..."
    on 01/11/24, Edward Diener <eldiener / earthlink.net> writes:

|While GC is nice, every language which has it needs a mechanism which
|forces the immediate destruction of a particular type of object when
|that object goes out of scope. Why ? Because without this feature, it is
|impossible to design objects which have resources which must be
|immediately released when the object is destroyed ( RAAI ).

??

Ruby and many other languages with GC (Java is in the same boat) allow
resource finalization when the object is "destroyed".

							matz.