At 00:55 09/04/2002, brad lafountain wrote: > Well i would have totally agreed with you yesterday.. but i have convinced >myself that there is use for aggregation. Me personally i would never use it. >But i can see somepeople using it.
It doesn't mean it's a good idea to add it. I used both, and yes, aggregation makes sense in some cases, but having them both in the language is like a supermarket of everything, and that's never good. >But giving the user a way to "MI" without having "MI" support(aggregation) >will >create alot of messy code. It wont even give the user a change to write >good OO >code. > >Can you explain why you can't see room for both of them? Aggregation is typically supported in userland, in the rare cases where it's really required (through wrapper methods that relay calls to a member object). Having them both will confuse people. Even people with some OO experience won't find it trivial to decide which they should use. Zeev -- PHP Development Mailing List <http://www.php.net/> To unsubscribe, visit: http://www.php.net/unsub.php
