I'd say yes. A compiler cannot know what the target VM's implementation of java.lang.Object.finalize() does, and hence whether calling it is necessary.
It can know that any *correct* implementation of Object.finalize is a no-op, so there is no reason it call it. It is hard to imagine any use for a non-empty Object.finalize; any VM-specific actions on object cleanup should be part of the run-time system instead.
An unnecessary call to java.lang.Object.finalize() won't hurt anyone.
Well, there is always performance ...
Besides, this would only be a compiler warning, and the user would be free to ignore it.
Many projects, including gcc itself, prohibit warnings. -- --Per Bothner [EMAIL PROTECTED] http://www.bothner.com/per/
_______________________________________________ Classpath mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/classpath
