> If you look at our code guidelines we specifically recomend against the
> artefacts of OO and recomend delegation where possible.
Delegation is an Object Programming pattern. There are all sorts of
patterns used in Object Programming. Saying that you recommend against the
"artefacts[sic] of OO" is not particularly contentful, other than to suggest
that you have a fuzzy prejudice against something you don't fully
understand. Since I believe that you are more talented that the comment
implies, I suggest that IF you deem it necessary to engage in this
discussion, that you be far more specific and clear about what you mean.
Now, if you mean to say that you don't believe that code sharing is
isomorphic with inheritance, then I agree with you. Inheritance is only one
aspect of Object Programming, and a generally poorly applied one at that,
IME. There are other means of code sharing within the Object Programming
paradigm.
Personally, I suggest that the rhetoric (and sarcasm from all sides) be
dropped, and that the focus be placed on what people ARE willing to do
constructively. From what I can see, most people are starting to do just
that: they are expressing what IS important to them, and what they ARE
willing to do, and the community is starting to jell around those common
points.
--- Noel
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
