At 14:25 23.05.2003, Andi Gutmans wrote:
>At 09:10 PM 5/22/2003 +0200, Marcus Börger wrote:
>>At 21:00 22.05.2003, Andi Gutmans wrote:
>>>At 08:31 PM 5/22/2003 +0200, Marcus Börger wrote:
>>>>At 18:26 22.05.2003, Wei He wrote:
>>>>>Hi,
>>>>>
>>>>>It seems that nobody cares about the aggregation bug. I know someone can
>>>>>avoid using aggregation by proxy calls or even method duplication like
>>>>>what I'm doing now. But what I'm warrying about is that what if it is a
>>>>>zend hash bug. It might affect some other places at expected moments and
>>>>>thus costing a lot of time of many people.
>>>>
>>>>
>>>>aggregation is still to be considered, whether it makes it into ze2 or
>>>>be dropped
>>>>or fixed or replaced by other oo goodies. (So far there was no final
>>>>decision from
>>>>zend).
>>>
>>>I remember agreeing that interfaces is going to be the aggregation
>>>alternative at the language level.
>>>If people want to build on top of this outside of Zend, although I'm not
>>>sure it's a good idea, this can be done.
>>
>>
>>Really? I can only remember that aggregation should be moved to the engine.
>>And aggregation is far away from interfaces. However there is still a
>>debate on
>>delegates open. They are close to aggregation when done at runtime. But i
>>would like them as in delphi and there they are done at compile time. So
>>actually i think we could have all three, can't we?
>
>I'm not quite sure what the difference between aggregation and delegation
>is. I usually think of delegation as aggregation with auto-proxy (although
>I guess it can also delegate to a non-aggregated object).
>I think this can all be implemented in user-land by using interfaces like
>in Java. I don't really want to bloat the engine anymore in this area
>unless it is something crucial.
From a design perspective i would appreciate this, however i see a need
for aggregation for BC.
It has been used by the intended audience of all those OO stuff.
marcus