On Oct 8, 2010, at 4:55 PM, Jesse A Wolfe wrote: > > > Single inheritance is already confusing enough and it's used primarily for > resource overrides and not scoping. > > > What I heard above is: people need resource defaults from multiple classes. > We could call the first one "inheritance" and the subsequent ones "mixins", > the way ruby does, but I think it doesn't actually clarify the situation.
I might agree with that, but I'm comfortable saying that calling it multiple inheritance doesn't really, either. I think there's actually a reasonable argument for a thin class that can only reasonably contribute variables and default, rather than resources. It would tend to be used as an aspect-like entity, rather than a parent class that you would normally expect to be related in function to the subclass. -- Brand's Shortcut: The only way to predict the future is to make sure it stays exactly the same as the present. --------------------------------------------------------------------- Luke Kanies -|- http://puppetlabs.com -|- +1(615)594-8199 -- You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-dev?hl=en.
