> That's one of many reasons to not do that. Specifically, one should
> employ class inheritance only when it involves overriding resource
> properties of the parent class.
We have a history of using class inheritence to override variables in
template's or add extra functionality the base class
> In general, I try and think of module dependencies and organization as
> a matter of composition. Discrete modules themselves should avoid
> establishing relationships with other modules. A module should,
> however, be diligent about managing the internal relationships of the
> classes and res
On Jan 23, 3:45 am, Jos Houtman wrote:
> Hello list,
>
> I am looking for advice/best-practices on how to handle inter module
> dependency's.
[...]
> Without stages we tried three ways of doing this:
> Creating a dependency chain between classes.
> Class['Ldap'] -> Class['Mysql'].
> This is ve
