Re: Design for Extension
- From: "Martin Ankerl" <martin.ankerl@xxxxxxxxx>
- Date: 17 Jan 2006 04:57:39 -0800
Actually I think "Design for Extension" can work very well with XP. The
difference from the normal approach is, that whenever you need to
extend a class, you cannot just make a subclass and override a method;
you need to refactor the base class and add an extension hook somewhere
first.
I think this might be a very good way of developing software. These are
the advantages/dissadvantages I see with this approach:
+ No beeing able to forgett to call super() in a subclass
+ Whenever behaviour of the base class is modified, it is done at a
place where it is designed to be extended.
- You have to be able to access and modify all the code you have to be
able to add hooks which can be very problematic with libraries.
--
Martin Ankerl | http://martinus.geekisp.com/
.
- References:
- Design for Extension
- From: Martin Ankerl
- Re: Design for Extension
- From: Thomas Weidenfeller
- Design for Extension
- Prev by Date: Re: copy data from JSTL tag to Java Variable.
- Next by Date: Re: Streaming over http
- Previous by thread: Re: Design for Extension
- Next by thread: Re: Design for Extension
- Index(es):
Relevant Pages
|
