A solution to the final classes problem

[Tom Eugelink]

It seems there have been enough comments suggesting to use final less generic, and from this email it is clear that the decision has been made otherwise. So be it. We tried :-)

On 2012-09-04 01:42, Richard Bair wrote:
> Every change we make to a class that is subclassable *will break somebody*.

That will also be the case when a class is merely used, so I find that not a strong argument pro-final.


> that somebody doesn't subclass and override a getter / setter to do "unnatural"

All exploits involving Java come, AFAIK, from the native plugin in the browser. My question about Swing and all its non final classes still remains unanswered. :-)

Tom