Issue #2053 has been updated by luke.
Category set to documentation
Status changed from Needs design decision to Accepted
lludwig wrote:
> Well I guess Puppet's :: naming throws me for a loop. I'm more used to the
> $this-> convention to explicitly do this. Yea I had no idea what was going
> on. I assumed 'include' started from the root, not the class it's currently
> in.
>
> So when you start with :: it refers to the root? So:
>
> ::classname::subclass
>
> $::classname::var
>
> Are valid? If so, that's good to know and maybe this is more of a
> documentation issue.
Yep, those are all valid.
And this class search seems most intuitive. E.g., with this class structure:
<pre>
class bar {}
class foo {
class bar {}
class baz {
include bar
}
}
</pre>
I'd expect foo::bar to get included, not ::bar.
----------------------------------------
Bug #2053: including a class with the same name subclass yields an unexpected
result
http://projects.reductivelabs.com/issues/2053
Author: lludwig
Status: Accepted
Priority: Normal
Assigned to:
Category: documentation
Target version:
Complexity: Unknown
Affected version: 0.24.7
Keywords:
If you create a subclass with the same as a class you include, you get an
unexpected result.
Test code is listed here.
http://pastie.org/409446
It appears that any include inside of subclass thinks it references itself
first.
----------------------------------------
You have received this notification because you have either subscribed to it,
or are involved in it.
To change your notification preferences, please click here:
http://reductivelabs.com/redmine/my/account
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Puppet Bugs" 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-bugs?hl=en
-~----------~----~----~----~------~----~------~--~---
