import question

[equinox at atw.hu]

>>
>> 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?



Marton Papp