On Saturday, January 21, 2012 22:28:20 [email protected] wrote: > >> Should not module C see c1? Because it cannot see it. Even if the > >> import > >> is not private. > > > > No. imports are private by default There's no point in marking them as > > private. If you want module C to see what module B is importing, then > > module B > > needs to import it publicly. e.g. > > > > module B; > > > > public import A; > > > > - Jonathan M Davis > > It makes sense. But did it always work like this?
It has for several years at minimum. But I don't know how it works in D1, and it may have worked differently in the very beginning of D2. I don't know. But as far as I know, it's always worked this way. - Jonathan m Davis
