On Fri, Sep 17, 2010 at 7:22 AM, Markus Roberts <[email protected]> wrote: > Here's a side question that may clarify something, at least for me: > what's the intended semantics of nesting classes? In other words, > what does it "mean" the real world (apart from language consequences > such as scoping / name spacing issues and implied dependencies, etc.) > to have one class nested inside another as opposed to being siblings > at the top level?
I was under the impression there wasn't any desired behavior other than namespacing and scoping. So if we take away scoping... > > -- Markus > ----------------------------------------------------------- > The power of accurate observation is > commonly called cynicism by those > who have not got it. ~George Bernard Shaw > ------------------------------------------------------------ > > -- > 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. > > -- 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.
