On Mon, Feb 15, 2010 at 5:58 AM, jcbollinger <[email protected]> wrote: > > > On Feb 13, 6:53 pm, Nigel Kersten <[email protected]> wrote: >> Do other people have a consistent naming system for distinguishing >> between sub-classes that are simply namespace children versus those >> that actually inherit from another class? > > I do not have such a system to offer, in part because I have never > conceived a need for one. Your setup is much more complicated than > mine, I think, so you surely have needs that I do not, but are you > certain this is one of them? In other words, what problem do you > solve by encoding that distinction into class names?
Not having to delve into a given class to work out how it behaves. I have a lot of part-time Puppet manifest maintainers. They don't do it regularly, and I've tried to keep a short leash on a lot of the more complicated Puppet features for this reason. It's by no means necessary. It's just bothering me, so I thought I'd see whether anyone else has an elegant solution... :) > > > John > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" 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-users?hl=en. > > -- nigel -- You received this message because you are subscribed to the Google Groups "Puppet Users" 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-users?hl=en.
