OMG -- Re: [frustration, sorry] Import conflict madness.

[Georg Wrede]

Derek Parnell wrote:
> On Sun, 18 Jun 2006 04:15:11 +1000, Chris Miller 
> <chris at dprogramming.com>  wrote:
> 
>> DMD 0.160:
>>     foo.d(1): import foo.std conflicts with bar.std at bar.d(1)
>>
>>
>> Of course, the code in test.d is a mistake, but look how unhelpful 
>> the  error message is. It will blame a library's code for a mistake 
>> the  library-user made.
> 
> 
> Maybe a message more like ...
> 
>     foo.d(6): std.string is not accessible
> 
> might be more useful for coders.
> 
>> Also notice that it's considering *private* imports, which shouldn't  
>> even be available to test.d.
> 
> 
> This has been broken for a *long* time now. Both "private" and 
> "package"  are just ignored by DMD for at least the last 5 or 6 
> releases. It used to  work but now it doesn't.

How is anyone new to D supposed to even consider using it when stuff 
like _private_ and _package_ are broken????????????????????????

This is both *elementary* and *essential* to any nontrivial project. It 
simply *has* to work.

"Would you buy a 3-wheel Ferrari?"

The first guys we lose this way are those who were considering D for 
real work (as opposed to hobby or tinkering).