Absolutely. +10 Dozens of times I've wanted and needed to push a member or method up into the super-class, and I've even needed to push them down (that's a trickier process, since you have to push it down to ALL current implmentations, and then probably modify each one ... after all, if they were all the same, why wouldn't they be in the super-class? ;-)
"Jacques Morel" <[EMAIL PROTECTED]> wrote in message adeddd$c78$[EMAIL PROTECTED]">news:adeddd$c78$[EMAIL PROTECTED]... > Along with Pull Up/Push Down Member they would indeed make a perfect > hierarchy refactoring tool. > > Please Please Please > "Paul Bradshaw" <[EMAIL PROTECTED]> wrote in message > ad8q8d$mms$[EMAIL PROTECTED]">news:ad8q8d$mms$[EMAIL PROTECTED]... > > I've posed this same feature request several times. Sometimes you want to > > keep the same root class name, and create a new derived class layer. > > Extract sub-class is exactly what you want and need. But it doesn't > exist. > > > > So obviously you get a +10 from me. It seems I need to extract a > sub-class > > far more often than I need to extract a super-class. Like, 10 to 1. > > > > "David Jansen" <[EMAIL PROTECTED]> wrote in message > > news:ad8ccj$4hp$[EMAIL PROTECTED]... > > > Is this a missing feature? I can't find it. > > > > > > Extracting a superclass is useful, but it's often the case that one > builds > > > too much behavior into a class and wants to extract a subclass. I > > suppose > > > you could do this with some renaming tricks + extract superclass, but > > that's > > > not very elegant. > > > > > > Thanks, > > > -David > > > > > > > > > > > > _______________________________________________ Eap-features mailing list [EMAIL PROTECTED] http://lists.jetbrains.com/mailman/listinfo/eap-features
