About Refactoring Patterns

Here there is a set of refactoring patterns which iŽd like to discuss with you. All comments, ideas and suggestions will be infinitely appreciated.

This page is the result of the research that is being taken in partial fulfillment of the requirements for the degree of Master in Sciences by the engineer Santiago L. Valdarrama.

At this moment, I completed BodyguardPattern. The other patterns will come in few days.

The BodyguardPattern is missing a "therefore" clause -- I assume the Therefore is something like "backup it up before you mess with it."

My reaction as someone who faces this problem on a daily basis is that this is what revision control is for. You check out a copy, make some refactorings, test it (honest), and then check in the new version. If your refactoring is defective, you back out the changes. In this way, refactoring is no different than adding a feature. -- BillTrost

The BodyguardPattern description doesn't cover any particulary backup method, so I think that CVS fits well into this pattern, however I will change it to show it clearly. Please, See the comments below BodyguardPattern -- SantiagoValdarrama.
EditText of this page (last edited July 11, 2004)
FindPage by browsing or searching

This page mirrored in WikiPagesAboutRefactoring as of July 17, 2004