• Larry Luther (11/11) Apr 29 2010 This code describes the concept:
• Ellery Newcomer (5/16) Apr 29 2010 It's probably not a bad idea to put A and B in the same module, but you
• BCS (4/6) Apr 30 2010 It's a side issue but: static constructors + cyclic imports == pain
• Larry Luther (1/1) Apr 30 2010 Thanks for your help.

"Larry Luther" <larry.luther dolby.com> writes:

This code describes the concept:

module a;
import B;

struct A { B *ptr; }

---------------------

module b;
import A;

struct B { A *ptr; }

-----------------------------

Can this be done?
Do both classes have to be in the same module?

Ellery Newcomer <ellery-newcomer utulsa.edu> writes:

On 04/29/2010 09:04 PM, Larry Luther wrote:
 This code describes the concept:

 module a;
 import B;

 struct A { B *ptr; }

 ---------------------

 module b;
 import A;

 struct B { A *ptr; }

 -----------------------------

 Can this be done?

sure

 Do both classes have to be in the same module?

It's probably not a bad idea to put A and B in the same module, but you 
shouldn't run into any trouble as you are, as long as you don't need any 
static constructors or destructors in either a or b.

BCS <none anon.com> writes:

Hello Ellery,

 as long as you don't
 need any static constructors or destructors in either a or b.

It's a side issue but: static constructors + cyclic imports == pain

-- 
... <IXOYE><

"Larry Luther" <larry.luther dolby.com> writes:

Thanks for your help.