danielv at netvision.net.il wrote:

> Cool.
> Can you explain what those inheritence dependencies mean exactly?
> I read you recent answer to Stephen that references them as giving
> trouble for cycles, but I'm not quite sure what cycles those would be in
> inheritence...
> 
> A swiki pointer would work for me, of course.
> 
> Daniel

The dependency is that class B inherits from class A. Thus A must be loaded
first. Now if class D inherits from class C, and A and D are in one module
and B and C are in another, then this causes a problem since both modules
need to be loaded before the other.

Henrik