Martin Stjernholm, Roxen IS @ Pike developers forum wrote:
Looks like cyclic resolver trouble. There are many (equally disgusting) ways to work around it. It's a bitch to fix. :(
Hmm.. are we up to it? (the fixing part) I would very much like to see it solved (I suppose I'm not alone ;) and wouldn't mind investing alot of effort into it, but won't be able to without support..
What I've seen this far is that it seems to be able to cope with the cyclic to some extent, but when more is added, it bails out..
If I understand the problem correctly, this is what happends:
compiling A... in A, find reference to B compile B in B, find reference to A already compiling A - error
This can't be the whole truth though, since this far it works fine for me, but toss in some more references between a few more modules, and it all comes down in pieces.. What seems to be the problem is when the compiler encounters static module references (A.moboo as opposed to A->fooboo).
Would it be possible to solve this by having the compiler first sweep through a program to add in all parts accessible by '.' and first after that compile its references, and finish up what's left?
I've tried to search in the archives of related discussions, but must have failed to use the right search terms..
//K