Peter Donald wrote:
On Fri, 22 Nov 2002 20:35, Stefano Mazzocchi wrote:Peter Donald wrote:On Fri, 22 Nov 2002 18:28, Stefano Mazzocchi wrote:[note that this reflects the inheritance model of OOP which this very community seems to have forgotten since Avalon doesn't make extensive use of it]Thats because most of us think OOP sucks. Give me COP or Modular programming over OOP any day.Interesting. I wonder who entitles you to speak for the rest of the crowd here.errr .. nice. You are here to help right?
yep, that's the plan
If you look at our code guidelines we specifically recomend against the artefacts of OO and recomend delegation where possible. I don't recall much discussion on OOP practices but it is quite common to discuss COP.
Great, let's do so.
Modular is just my approach to things - it is also the same approach used by "enterprise" level frameworks ala EJB / DNA (or whatever it is called nowadays).I think that Avalon would gain a lot in using inheritance at a containment level.
If containers extend one another:
1) it increases interoperability (because they share common code and behavior)
2) it reduces maintenance costs (if code is extended, bugfixes applied to an extended container will apply to all containers that extend)
There is also one major difference in what has been done until today around here:
1) development must be done over consensus between the developers that work on the different containers
I must state that I consider all three points to be positive for the Avalon community and for the perceived solidity of Avalon from the outside.
--
Stefano Mazzocchi <[EMAIL PROTECTED]>
--------------------------------------------------------------------
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
