If ModA is Car and ModB is CarEngine then I understand that the Car wants to import CarEngine because Car HasA CarEngine, I don't see why would CarEngine import Car. Even if it later keeps a IsIn reference.
The concept makes about as much sense as multiple inheritance. It looked like a good idea at first, but it causes too many subtle and hard to debug problems. Which is why things like mixins were invented. Though of course it means a bit of refactoring, instead of merging two classes and hoping for the best.
Jenda
Enoch was right!
Enjoy the last years of Rome.
In reply to Re^3: Mini-Tutorial: Mutual Use of Exporting Modules
by Jenda
in thread Mini-Tutorial: Mutual Use of Exporting Modules
by ikegami
For: | Use: | ||
& | & | ||
< | < | ||
> | > | ||
[ | [ | ||
] | ] |