The commonly accepted two use cases are (1) for safety-net finalizers in
older code (ensure resource is closed, but not preferred means), and (2)
for native peers for finalizer chaining into native JNI calls that must
have their finalizers called.
Sincerely,
Joseph
--
You received this mess
I think even in Java there are few cases where you should rely on finalize.
Actualy you should not rely on it at all
2012/8/24 Harold Comere
> Hi,
>
> Thank you for answers !
>
> I am using GWT for 3D purpose with WebGL.
> When i am destroying an object from the 3D sce
used by any other object.
In JAVA, the finalize() method done the trick as the garbage collector
checks references to destroy unused objects.
If JavaScript do not do that, i think i have to do a kind of smart pointer
by myself.
Regards,
Harold
2012/8/24 Joseph Lust
> Generally speaking, there
Generally speaking, there is no reason you should need finalize either as
it is a anti-pattern in all but a very few cases. However, for items like
widgets, you can do cleanup in the OnDetach and OnUnload methods.
Sincerely,
Joseph
--
You received this message because you are subscribed to
On Friday, August 24, 2012 12:28:27 PM UTC+2, Harold wrote:
>
> Hi all,
>
> I can not find the info on the web but :
>
> Does finalize() method works properly after gwt compilation ?
>
>
No. There's no such thing in JavaScript so it cannot be emulated.
--
You rece
Hi all,
I can not find the info on the web but :
Does finalize() method works properly after gwt compilation ?
Regards,
Haroldli
--
You received this message because you are subscribed to the Google Groups
"Google Web Toolkit" group.
To post to this group, send email to google-w
