I think that the key problems are: (a) It's unclear if the current behavior is the 'right thing' to do, as demonstrated by Kristian and yourself... (b) I personally think that it pretty much set the final decision on MI (as in, there won't be MI), because having both aggregation and MI in a language is kind of clumsy and messy. That's not much of a big deal I guess, but people should realize that.
Zeev At 12:07 PM 4/5/2002, Stig S. Bakken wrote: >On Fri, 2002-04-05 at 11:05, Hartmut Holzgraefe wrote: > > Yasuo Ohgaki wrote: > > > --disable-experimental-aggregate and > > > --disable-experimental-overload? > > > > > > Just in case we really want to make it optional and have new way > > > for overloading/multiple inheritance. > > > We can document these features as EXPETIMENTAL as long as we want, > > > right? > > > > which brings us back to the discussion that EXPERIMENTAL stuff > > should not be packed into releases or should at least be disabled > > by default (like linux configuration does with its "enable experomental > > stuff" which is disabled by default) > >If these features are going to be marked as experimental because they >have not been accepted by php-dev, php-dev should at least make an >effort to comment on them so we can resolve this. > >I don't want to have overload and aggregate lingering as experimental >features. If people have objections, bring them on so we can talk. > > - Stig > > >-- >PHP Development Mailing List <http://www.php.net/> >To unsubscribe, visit: http://www.php.net/unsub.php -- PHP Development Mailing List <http://www.php.net/> To unsubscribe, visit: http://www.php.net/unsub.php
