On Sep 17, 2010, at 10:22 AM, Markus Roberts 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?
The only functionality I can think of is affecting the search path, which
determines lookup of unqualified class and definition names.
I.e., no affect on variable scope at all.
--
To be positive: To be mistaken at the top of one's voice.
-- Ambrose Bierce
---------------------------------------------------------------------
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.
