On Tuesday, December 4, 2012 9:21:53 PM UTC-6, Gary Larizza wrote: > > It's a bit deeper than that, > > Nesting a class definition inside of a class definition will result in a > class namespaced as first_class::second_class. >
That is, nesting will result *only* in a class *definition* namespaced as Gary describes. It does itself not cause the nested class to be assigned to those nodes to which its containing class is assigned. > Because of this, you'll need to "include mock::my_file" in your node > declaration. > Or add that 'include' statement in the body of class mock, after the nested class definition. That would produce exactly the result you expected. If you're going to do that, however, then you should consider why you wanted a nested class in the first place. > > It's recommended to keep one class definition per file and to follow the > Module patterns [2] and Style Guide [3] when doing so. > > [1] http://docs.puppetlabs.com/learning/modules1.html > [2] http://docs.puppetlabs.com/guides/style_guide.html > > Indeed so. To be a bit more blunt: don't lexically nest classes. Nesting provides little more than namespacing, which you can get explicitly instead. Furthermore, nested classes may be missed by the autoloader, and also by humans. Class nesting is mostly pain for little, if any, gain. John -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/_SW7exzdl-IJ. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
