I am the sort of person who would re-write code, rather than adjust it. However, my re-write will not necessarily work as well as the original code. Even if it did, how could I be sure that it did?
This book is intended to show you how to modify existing code in a safe way. The aim of changing ... Read review
Your class library works, but could it be better? Refactoring: Improving the Design of ... more
Existing Code shows how refactoring can make object-oriented code simpler and easier to maintain. Today, refactoring requires considerable design know-how, but...
Postage & Packaging: £2.75 Availability: Usually dispatched within 1-2 business days...
Your class library works, but could it be better?Refactoring: Improving the Design of ... more
Existing Codeshows how refactoring can make object-oriented code simpler and easier to maintain. Today, refactoring requires considerable design know-how, but on...
Postage & Packaging: £2.75 Availability: Usually dispatched within 1-2 business days...
Advantages: Straightforward and common sense Disadvantages: Experienced coders might find this patronising
...how to avoid it by refactoring the code before you make your behaviour changes.
The book is written with Java examples but reads well for C++. You will have done many of these refactorings already, but this book shows you how to do them in a more foolproof way.
Check out the refactoring web-site for more info and refactorings that are not in the book: http://www.refactoring.com/
... more
I am the sort of person who would re-write code, rather than adjust it. However, my re-write will not necessarily work as well as the original code. Even if it did, how could I be sure that it did? This book is intended to show you how to modify existing code in a safe way. The aim of changing the code is to improve its underlying design. The aim of changing the underlying design is to allow for a particular expansion to be made, or for the code to be more understandable and, therefore, maintainable.
We all change code when it does not suit us but are we really improving it? This book will give you some hard and fast ways of detecting "bad-smelling" code. If you encounter such code, it shows you how to make it smell nice again. If you are about to make some code smell bad, you can be aware of this and know how to avoid it by refactoring the code before you make your behaviour changes.
The book is written with Java examples but reads well for C++. You will have done many of these refactorings already, but this book shows you how to do them in a more foolproof way.
Check out the refactoring web-site for more info and refactorings that are not in the book: http://www.refactoring.com/
