> > > > imho this shouldve been the default java convention. it takes more thought > and analysis to design something to be overridable.
don't know about that, i think i would have hit my head against the wall way way more often then i do now. Sometimes i just HAVE to override behavior of swing components for example now they have pieces that are packages scope (textformatters for example for the jformatted textfield) thats HORRIBLE. The problem with automatic everything final that nobody thinks about it and in the end you have something that can only be used by copy pasting whole classes. The shit thing is that that can't be done for example with the jformattedtextfield because thats not 1 class thats whole packages... I think it is most of the time the responsibility of the developer itself. If i want to override then i want to override where final in my eyes is good for is 2 things: when we depricate methods, make the final but more if we don't really want it to be public api but for this we should have another keyword... johan
