I don't agree with you, Sergei. You /implement/ abstract methods (interface methods are abstract methods, too) and you /override/ methods, that already have an implementation in the super classes.
In other words: You *must* implement abstract methods to use the class (to get a non-abstract class). You *may* override methods to change the super-class' behavior. Therefor I think, the current behavior is ok. Tom At 19:12 17.04.2002 -0500, you wrote: >Kirk Woll wrote: > >>But what do you both mean? Oddly, the behavior Elizabeth wanted is >>precisely the way Idea already behaves. Abstract methods declared in a >>super class do in fact only show up in the "implement methods" dialog. >>Which is as it should be. > >8) Well it shouldnt be. You do extend abstract class in order to get final >class >therefore any method that you about to make with same signature as parent >class is overriding - so methods should be in "override". And you do implement >interface - so whatever methods are in interfaces - they should be in >"implement" menu. > >I.e i know that IDEA does put abstract methods into "implement" menu, but >it doesnt >change fact that they shouldnt be there from purely Java point of view 8) >And no - i dont >want that straighten out, b/c too many of us already got used to it 8) > > >Cheers, >Sergei. _______________________________________________ Eap-list mailing list [EMAIL PROTECTED] http://www.intellij.com/mailman/listinfo/eap-list
