Revision as of 13:33, 26 March 2009 edit JulesH (talk \| contribs) Extended confirmed users 5,584 edits →Refactoring to improve performance? ← Previous edit		Revision as of 16:01, 26 March 2009 edit undo JulesH (talk \| contribs) Extended confirmed users 5,584 edits No edit summary Next edit →
Line 27: ::In software engineering, the term 'factorization' was introduced by Peter Deutsch. I don't have the source paper right now, but I believe that he defined factorization to be the distribution of responsibilities among classes in object-oriented software system. So, refactorization should mean re-distribution of these responsibilities. [[User:Pdemb\|Pdemb]] 19:46, 17 September 2006 (UTC) :::I know this is an old discussion, but just in case anyone's still interested, the earliest use of the term "factorization" (or at least a related term) to refer to splitting responsibilities of code between different modules that I'm aware of was by [[Edsger Dijkstra]] in his 1972 Turing Award Lecture; he used the term "well-factored" on a number of occasions to describe software that adhered to good design principles. Quite clearly, he was not talking about object-oriented systems at the time. [[User:JulesH\|JulesH]] ([[User talk:JulesH\|talk]]) 16:01, 26 March 2009 (UTC) == Which type of testing ensures that refactoring does not change the behavior of the code ==

Talk:Code refactoring: Difference between revisions