[frustration, sorry] Import conflict madness.

[BCS]

Derek Parnell wrote:
> On Sun, 18 Jun 2006 03:49:44 +1000, Deewiant  
> <deewiant.doesnotlike.spam at gmail.com> wrote:
[...]
>> Seems to me that using "private import" instead of "public import" 
>> (the  default) might help in locating this. When using "private 
 >> import A;" in a module  B, any other module that imports B does
>> not automatically import A. I have long felt that private should 
 >> be the default.
>  
> I have yet to find a *need* for public imports.
> 

A single-point-of-access module for a lib might count as a use. OTOH I 
have taken to doing all imports as private.

import myBigLib;

<code file="myBigLib.d>
public import theFirstFile;
public import theSecondFile;
public import theThirdFile;
...
</code>