Comments on: Refactoring Day 8 : Replace Inheritance with Delegation http://lostechies.com/seanchambers/2009/08/07/refactoring-day-8-replace-inheritance-with-delegation/ Just another LosTechies site Thu, 13 Sep 2012 07:11:00 +0000 hourly 1 http://wordpress.org/?v=3.4.2 By: Slawek Ludwiczak http://lostechies.com/seanchambers/2009/08/07/refactoring-day-8-replace-inheritance-with-delegation/#comment-626 Slawek Ludwiczak Sun, 03 Jun 2012 21:09:00 +0000 /blogs/sean_chambers/archive/2009/08/07/refactoring-day-8-replace-inheritance-with-delegation.aspx#comment-626 extremely useful posts about refactoring, thanks Sean! :) extremely useful posts about refactoring, thanks Sean! :)

]]> By: Scott Sherin http://lostechies.com/seanchambers/2009/08/07/refactoring-day-8-replace-inheritance-with-delegation/#comment-386 Scott Sherin Tue, 11 Aug 2009 18:50:28 +0000 /blogs/sean_chambers/archive/2009/08/07/refactoring-day-8-replace-inheritance-with-delegation.aspx#comment-386 Your example would be better refactored into an interface. Also why are you using a private property instead of just a private field? It's good to make all public variables into properties so if you need the flexibility later you don't break references. Private fields will have no references outside your class so you can refactor them into properties if needed. The original example gets the idea across much better than this one. Your example would be better refactored into an interface. Also why are you using a private property instead of just a private field? It’s good to make all public variables into properties so if you need the flexibility later you don’t break references. Private fields will have no references outside your class so you can refactor them into properties if needed.

The original example gets the idea across much better than this one.

]]> By: Thomas Eyde http://lostechies.com/seanchambers/2009/08/07/refactoring-day-8-replace-inheritance-with-delegation/#comment-385 Thomas Eyde Sun, 09 Aug 2009 11:06:38 +0000 /blogs/sean_chambers/archive/2009/08/07/refactoring-day-8-replace-inheritance-with-delegation.aspx#comment-385 This is a very useful refactoring. But, as always, there are these icky corner cases: I usually end up in the need of this refactoring, when I create new, but similar classes. At first, it makes perfectly sense to extract super class. It's not until later, when I discover an unfortunate mix between orchestration and implementation, I see that delegation will make clearer code. This is a very useful refactoring. But, as always, there are these icky corner cases: I usually end up in the need of this refactoring, when I create new, but similar classes.

At first, it makes perfectly sense to extract super class. It’s not until later, when I discover an unfortunate mix between orchestration and implementation, I see that delegation will make clearer code.

]]>