> It is currently legal to do
>
> class A {
> class disable inherits A {
> ...
> }
> }
>
> and then "include A::disable".
It is also legal (and imho the better way) to put the disable class in
its own file. As far as I remember this doesn't make any difference,
except using more inodes (as once somebody nagged on IRC).
Anyway related to that discussion I might want to remember the other
thread about autoloading where afair it was more or less consensus to
enforce the policy that there should be only one class or define in a
file corresponding to its name. So if we would do these
autolookup/loading improvements (mainly perfomance) we would anyway get
rid off that nested classes syntax. right?
~pete
--
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.
