On Friday 27 February 2004 09:22, [EMAIL PROTECTED] wrote: > allowing that Niclas is from Sweden
:o) What that got to do with it ? Stupid Blonde? > I think he agrees with you that inheritance is good in > some circumstance and bad in others. Of course there is, but far for as common as people have in there mind. Scott(?) brought up "java.io". I think that is a 'classic case' of good inheritence, yet it excel because of the delegation model, and I think it is a "mistake" that InputStream is not an interface. Another, IMHO, example of inheritence vs delegation/interfaces is the difference between NetBeans and Eclipse. NB is one hell of a mess, and I accredit a lot of that to excessive inheritence, yet the power horses behind it defend it as a good choice. Eclipse's model is much neater and friendlier to work with. Bottom line, we are taught by many sources about inheritence, and then go out and over do it. Almost always we end up with too much code in the superclasses (due to inaccurate understanding of the problem from the early use-cases) and tricky maintenance of that superclass, since too many things start depending on behaviour instead of stipulated contract. The extra effort you are encourage to do in Avalon, could be called a 'guide' to be more aware of this issue. Cheers Niclas -- +---------//-------------------+ | http://www.bali.ac | | http://niclas.hedhman.org | +------//----------------------+ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
