On Tue, Sep 29, 2009 at 10:13 AM, Rickard Öberg <[email protected]> wrote:
> The main problem here is that the class is final, and it shouldn't be. IMO > there's a bit of trigger-happiness going on with the "final" keyword in the > codebase. "final" is good, but don't overuse it. On the contrary, overuse is safe, as it is always possible to go "non-final" but never the other way around. Designing for subclassing is difficult and IMHO most classes that are "intended" to be subclassed actually fail to some point, and those that "don't care" fail miserably. My standpoint on this is crystal clear; Until someone shows a use-case for subclassing, "final" stays. In this case; I assume that you marked the methods final when you removed it on the class... Cheers -- Niclas Hedhman, Software Developer http://www.qi4j.org - New Energy for Java I live here; http://tinyurl.com/2qq9er I work here; http://tinyurl.com/2ymelc I relax here; http://tinyurl.com/2cgsug _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
