http://winterdom.com/2007/07/regionsandreadability by dæmons be driven Tue, 16 Mar 2010 06:33:03 +0000 http://wordpress.org/?v=2.9.2 hourly 1 http://winterdom.com/2007/07/regionsandreadability/comment-page-1#comment-172 Tomas Restrepo Mon, 30 Jul 2007 07:15:19 +0000 http://winterdom.com/2007/07/regionsandreadability#comment-172 @David: Absolutely agree about extracting a role interface; I do practice it a number of times, but others I'm stuck with the design the base class library came with :) (Though, interestingly enough, the data reader case almost matches this, as most of the accessors are in IDataRecord, from which IDataReader inherits). @David: Absolutely agree about extracting a role interface; I do practice it a number of times, but others I’m stuck with the design the base class library came with
(Though, interestingly enough, the data reader case almost matches this, as most of the accessors are in IDataRecord, from which IDataReader inherits).

]]> http://winterdom.com/2007/07/regionsandreadability/comment-page-1#comment-171 Dave Mon, 30 Jul 2007 06:48:02 +0000 http://winterdom.com/2007/07/regionsandreadability#comment-171 These are good reasons, I'd say. I'd say in the case of "Lots a Related Methods" I often extract a role interface. In which case the grouping interface implementation heuristic comes into place. I also agree that when you've got a class with lots of role interfaces regions <i>can</i> help express intent. These are good reasons, I’d say. I’d say in the case of "Lots a Related Methods" I often extract a role interface. In which case the grouping interface implementation heuristic comes into place. I also agree that when you’ve got a class with lots of role interfaces regions can help express intent.

]]>