I believe the extract subclass we are talking about is a lot simpler. It is an extract superclass with a little twist: instead of asking the user the name of the base class, you keep the old name for the base class and ask for the name of the derived class. It avoids a potentially large renaming at all use points. Instead extract subclass only need to consider allocation points & class/interface definition. BTW this should work on classes and interfaces.
Jacques "Dmitry Lomov" <[EMAIL PROTECTED]> wrote in message adn06n$7kj$[EMAIL PROTECTED]">news:adn06n$7kj$[EMAIL PROTECTED]... > Hi, > As for "Pull up/push down" refactorings, they are planned for Ariadna. > Do you think we need a separate "extract subclass" if we have those two? > Making an empty descendant class and then moving neccessary stuff there > seems > to be easy enough. What would you say? > _______________________________________________ Eap-features mailing list [EMAIL PROTECTED] http://lists.jetbrains.com/mailman/listinfo/eap-features
