From: Tim Wilkinson (tim@transvirtual.com)
Date: Tue Oct 13 1998 - 14:00:40 EDT
I'd be happy to see some intelligent finalising go back it - I just needed
to get finalizing working since it wasn't handled correctly in B1. I don't
however want to assume that Object has a zero functionality finalizer so a
method which looks at the code and goes - ah! it just returns - is a fine
way to work this out.
Cheers
Tim
Godmar Back wrote:
> Hi, while going through the recent changes, I noticed that class.final
> has disappeared. I believe we're taking a big hit by doing so.
> I know for sure that we lose bitterly in artificial gc benchmarks;
> I would suspect some impact under normal use as well.
>
> Basically, what needs to be done is to analyze whether a class has a
> non-empty finalizer (in most cases, classes will inherit the empty
> finalizer of java.lang.Object), and if so, set class.final and finalize.
> Whether a finalizer is empty or not should be simply inferred from the
> length of the code---or am I missing something here?
>
> What do you think?
>
> - Godmar
-- Tim Wilkinson Tel: +1 510 704 1660 Transvirtual Technologies, Inc., Fax: +1 510 704 1893 Berkeley, CA, USA. Email: tim@transvirtual.com
This archive was generated by hypermail 2b29 : Sat Sep 23 2000 - 19:57:00 EDT