On Aug 23, 12:53 pm, David Kavanagh <dkavan...@gmail.com> wrote: > It seems there's a problem including a class multiple times. By > stating that one class requires another, you formalize the dependency, > but don't actually have an include. What you do then is to include the > class in your main implementation which uses that class. That way, if > you have several classes that depend on one other class, it is > included once at the top level, but used many places (where it is > required). > Is that as clear as I think it is?
Not to me. To the extent that I understand what you're saying, it doesn't sound right. The 'require' function does everything that 'include' does (and then some), so using 'require' vs. 'include' does nothing to address any problems with multiple inclusion. Furthermore, the issues with multiple inclusion are sufficiently mild that my preferred coding practice is to rely on including classes everywhere they are needed. To my knowledge, multiple inclusion is problematic only in these cases: 1) When the included class uses a variable resolved via dynamic scoping, and that variable may be resolved differently at different points of inclusion. That doesn't bother me much, because if ever that happens then it reflects a design error in the manifests anyway. There are alternative, better ways to feed data to your classes than dynamically scoped variables. 2) When the class to 'include' is parameterized (but I consider this more a flaw in the design of the parameterized class framework than in the 'include' function). John -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. 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.
