Re: Error in opening the Library module file


Jugoslav Dujic wrote:
Mike wrote:
| Mike wrote:
|| Originally they pick up some modules, however, they didn't pick up
|| modules which
|| are calling each other. I think this problem is called cyclic
|| dependencies, right?

Right, "cyclic" or "circular". What you had is (as far as I can tell)
allowed by the standard but it will confuse most compilers -- they
expect the dependency hierarchy to be "tree-like" and cannot tell which
module should be compiled first (esp. when they're in the same source
file).

By all means, try to avoid the situation -- the solution is often
to move the mutually shared stuff to a third module, which is
compilable separately.
How to avoid cyclic dependency at first?
What's the general idea to avoid it?

Mike

.

Relevant Pages