Working Effectively with Legacy CodePrentice Hall, 2004 - 434 Seiten This book provides programmers with the ability to cost effectively handlecommon legacy code problems without having to go through the hugelyexpensive task of rewriting all existing code. It describes a series of practicalstrategies that developers can employ to bring their existing softwareapplications under control. The author provides useful guidance about how touse these strategies when refactoring or making functional changes to codebases. One of the book's key points is that it teaches developers to write teststhat can be used to make sure they are not unintentionally changing theapplication as they optimize it. Examples are provided in Java, C++, and Csharp, and the book assumes that the reader has some knowledge of UMLnotation. Strategies using UML and code in C++ and Java primarily whilelanguage independent advice will be delivered in side bars and appendices forlanguage specific users. |
Im Buch
Ergebnisse 1-3 von 24
Michael C. Feathers. Extract Implementer Extract Implementer Extract Interface ( 362 ) is a handy technique , but one part of it is hard : naming . I often run into cases where I want to extract an interface but the name I want to use is ...
... Extract Implementer is relatively simple when the source class doesn't have any parent or child classes in its inheritance hierarchy . When it does ... Extract Implementer that can be converted into an interface . EXTRACT IMPLEMENTER 359.
... Extract Interface ( 362 ) and picking different names for your interfaces . It is a far more direct refactoring . Extract Implementer Extract Interface Extract Interface In many languages , Extract Interface. EXTRACT IMPLEMENTER 361.
Inhalt
The Mechanics of Change | 1 |
Changing Software | 55 |
DependencyBreaking Techniques | 323 |
Urheberrecht | |
3 weitere Abschnitte werden nicht angezeigt.