On Sun, Jan 9, 2011 at 9:00 PM, Greg Brown <gk_br...@verizon.net> wrote:
> There are select cases where the final modifier is being used but not > strictly needed, and these are preventing developers from fully utilizing the > builder pattern calathus has suggested. Other classes (such our our > "structs") would remain final. I am just saying that "By allowing people to freely override classes, you are exposing Pivot to a whole range of compatibility issues in the future. The subclasses becomes part of *your* concern space, since more often than not you can't easily distinguish the contract between the supertype and the subtype. Swing is classic example, Wicket is another but realized it after a while and started a delegation pattern in parallel." YMMV, but in general; I would strong discourage using inheritance as an extension/customization mechanism. Been there, burned myself a lot and won't go there again. Cheers -- Niclas Hedhman, Software Developer http://www.qi4j.org - New Energy for Java I live here; http://tinyurl.com/3xugrbk I work here; http://tinyurl.com/24svnvk I relax here; http://tinyurl.com/2cgsug
