Re: Large Java classes wanted
"K" <[email protected]> Tue, 23 Feb 2010 23:55:05 -0000
| Newsgroups | gmane.comp.programming.refactoring |
|---|---|
| Message-ID | <[email protected]> |
Let me try to be clarify what I'm doing. My research involves programmatically detecting groups of methods and attributes within a class that are highly associated/cohesive. I want to reduce the amount of programmer effort involved in the Extract Class refactoring that you're describing. Regards, Keith Cassell --- In [email protected], J Arrizza <cppgent0@...> wrote: > > On Mon, Feb 22, 2010 at 5:23 PM, Heinrich Breedt > <heinrichbreedt@...> wrote: > You will use two basic refactorings: Extract Method and Extract Class. > You will use Extract Method most of the time, but that's just a > stepping stone to the real big-bang-for-buck workhorse, Extract Class. > > The basic thing to realize is that a very large class is a set of > smaller classes intertwined together. And that a class is a cohesive > set of methods that associate strongly with each other and associate > (very) strongly with a small set of variables. > > 1) The primary strategy to use is: > > a) isolate one member variable of the large class and extract it into > a private class as a public variable > ... ------------------------------------ Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/refactoring/ <*> Your email settings: Individual Email | Traditional <*> To change settings online go to: http://groups.yahoo.com/group/refactoring/join (Yahoo! ID required) <*> To change settings via email: [email protected] [email protected] <*> To unsubscribe from this group, send an email to: [email protected] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/